{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-0497 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-0497 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-0497 is a high-severity vulnerability in n/a, published on 21 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-0497 and fix it if it is affected.\n\nWhat it is: CVE-2005-0497 is a high-severity vulnerability in n/a, published on 21 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2005-0497 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2005-0497/ (Markdown: https://insights.sbomify.com/CVE-2005-0497/index.md)","id":"CVE-2005-0497","markdown":"https://insights.sbomify.com/CVE-2005-0497/index.md","name":"CVE-2005-0497","record":{"aliases":["GHSA-67gx-qjmq-5fjr"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"ADP Elite System","requires_auth":"low_privilege","summary":"Authenticated users can escalate privileges to root by uploading a malicious profile file that modifies environment variables.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"elite_system_max_9000","vendor":"adp"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"ADP Elite System Max 9000 allows remote authenticated users to gain privileges by uploading a .profile that sets the ADPROOT environment variable to the root directory.","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 n/a","id":"CVE-2005-0497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2005"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2005-0498"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2005-0496"},"products":["n/a"],"published":"2005-02-21","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Authenticated users can escalate privileges to root by uploading a malicious profile file that modifies environment variables.","url":"https://insights.sbomify.com/CVE-2005-0497/"}