{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-47254 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-47254 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47254 is a medium-severity vulnerability in 2N Access Commander, published on 5 Nov 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-47254 and fix it if it is affected.\n\nWhat it is: CVE-2024-47254 is a medium-severity vulnerability in 2N Access Commander, published on 5 Nov 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: There is no known exploitation of CVE-2024-47254 in the wild and no public exploit code.\n\nAffected product: 2N Access Commander. 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-47254/ (Markdown: https://insights.sbomify.com/CVE-2024-47254/index.md)","id":"CVE-2024-47254","markdown":"https://insights.sbomify.com/CVE-2024-47254/index.md","name":"CVE-2024-47254","record":{"aliases":["GHSA-rxqh-7qx7-59m3"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Access control system","requires_auth":"high_privilege","summary":"Attackers can escalate privileges to gain root access on 2N Access Commander systems due to insufficient data authenticity verification.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Axis","cpe":[{"product":"access_commander","vendor":"2n"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-807","name":"Reliance on Untrusted Inputs in a Security Decision"}],"description":"In 2N Access Commander versions 3.1.1.2 and prior, an Insufficient \nVerification of Data Authenticity vulnerability could allow an attacker \nto escalate their privileges and gain root access to the system.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in 2N Access Commander","id":"CVE-2024-47254","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in 2N Access Commander","id":"CVE-2024-47255"},"packages":[],"prev":{"headline":"Path traversal in 2N Access Commander","id":"CVE-2024-47253"},"products":["2N Access Commander"],"published":"2024-11-05","related":[{"cvss_score":8.8,"headline":"OS Command Injection over API","id":"CVE-2025-59783","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":7.2,"headline":"Path traversal in 2N Access Commander","id":"CVE-2024-47253","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":6.9,"headline":"Log Pollution - Control Characters Not Escaped","id":"CVE-2025-59784","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":6,"headline":"Cookies are not Invalidated upon Logout and Password Change","id":"CVE-2025-59786","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":5.3,"headline":"API - Insufficient Input Validation","id":"CVE-2025-59785","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":5.3,"headline":"HTTP 5XX Internal Server Errors","id":"CVE-2025-59787","kev_date_added":null,"published":"2026-03-04"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-09","vendors":["2N"]},"summary":"Attackers can escalate privileges to gain root access on 2N Access Commander systems due to insufficient data authenticity verification.","url":"https://insights.sbomify.com/CVE-2024-47254/"}