{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27301 exists.","fix":"No fix has been published for CVE-2024-27301 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-27301 is a high-severity vulnerability in root3nl SupportApp, published on 14 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-27301 and fix it if it is affected.\n\nWhat it is: CVE-2024-27301 is a high-severity vulnerability in root3nl SupportApp, published on 14 Mar 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27301 exists.\n\nAffected product: root3nl SupportApp. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-27301/ (Markdown: https://insights.sbomify.com/CVE-2024-27301/index.md)","id":"CVE-2024-27301","markdown":"https://insights.sbomify.com/CVE-2024-27301/index.md","name":"CVE-2024-27301","record":{"aliases":["GHSA-jr78-247f-rhqc"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Apple device management app","requires_auth":"low_privilege","summary":"Attackers can escalate privileges to root by injecting code into the user's zsh environment file, which is loaded during the application's post-installation script.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"support_app","vendor":"root3"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Support App is an opensource application specialized in managing Apple devices. It's possible to abuse a vulnerability inside the postinstall installer script to make the installer execute arbitrary code as root. The cause of the vulnerability is the fact that the shebang `#!/bin/zsh` is being used. When the installer is executed it asks for the users password to be executed as root. However, it'll still be using the $HOME of the user and therefore loading the file  `$HOME/.zshenv` when the `postinstall` script is executed.\nAn attacker could add malicious code to `$HOME/.zshenv` and it will be executed when the app is installed. An attacker may leverage this vulnerability to escalate privilege on the system. This issue has been addressed in version 2.5.1 Rev 2. All users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Privilege Escalation Abusing installer in SupportApp","id":"CVE-2024-27301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Authorization Bypass Through User-Controlled Key in go-zero","id":"CVE-2024-27302"},"packages":[],"prev":{"headline":"phpMyFAQ Stored XSS at user email","id":"CVE-2024-27300"},"products":["SupportApp"],"published":"2024-03-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["root3nl"]},"summary":"Attackers can escalate privileges to root by injecting code into the user's zsh environment file, which is loaded during the application's post-installation script.","url":"https://insights.sbomify.com/CVE-2024-27301/"}