{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-0169 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-0169 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-0169 is a critical vulnerability in n/a, published on 16 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-0169 and fix it if it is affected.\n\nWhat it is: CVE-2009-0169 is a critical vulnerability in n/a, published on 16 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2009-0169 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-2009-0169/ (Markdown: https://insights.sbomify.com/CVE-2009-0169/index.md)","id":"CVE-2009-0169","markdown":"https://insights.sbomify.com/CVE-2009-0169/index.md","name":"CVE-2009-0169","record":{"aliases":["GHSA-qx89-xhcp-6f84"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Java Access Manager","requires_auth":"low_privilege","summary":"Authenticated sub-realm administrators can escalate privileges to root realm access by creating an amadmin account.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"java_system_access_manager","vendor":"sun"}],"cvss":{"score":9,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:S/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Sun Java System Access Manager 7.1 allows remote authenticated sub-realm administrators to gain privileges, as demonstrated by creating the amadmin account in the sub-realm, and then logging in as amadmin in the root realm.","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-2009-0169","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2009"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2009-0170"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2009-0168"},"products":["n/a"],"published":"2009-01-16","related":[{"cvss_score":9.3,"headline":"Auth bypass in n/a","id":"CVE-2008-2705","kev_date_added":null,"published":"2008-06-16"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2008-2945","kev_date_added":null,"published":"2008-06-30"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2007-5152","kev_date_added":null,"published":"2007-10-01"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2006-0531","kev_date_added":null,"published":"2006-02-04"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2007-5153","kev_date_added":null,"published":"2007-10-01"},{"cvss_score":6,"headline":"Information disclosure in n/a","id":"CVE-2009-0170","kev_date_added":null,"published":"2009-01-16"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Authenticated sub-realm administrators can escalate privileges to root realm access by creating an amadmin account.","url":"https://insights.sbomify.com/CVE-2009-0169/"}