{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-5014 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-5014 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-5014 is a high-severity authentication bypass vulnerability in n/a, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-5014 and fix it if it is affected.\n\nWhat it is: CVE-2009-5014 is a high-severity authentication bypass vulnerability in n/a, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2009-5014 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-5014/ (Markdown: https://insights.sbomify.com/CVE-2009-5014/index.md)","id":"CVE-2009-5014","markdown":"https://insights.sbomify.com/CVE-2009-5014/index.md","name":"CVE-2009-5014","record":{"aliases":["GHSA-px96-54jm-q7g6"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python web framework","requires_auth":"none","summary":"Remote attackers can bypass authentication in TurboGears2 by forging authorization cookies due to a weak default salt.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"turbogears2","vendor":"turbogears"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"The default quickstart configuration of TurboGears2 (aka tg2) before 2.0.2 has a weak cookie salt, which makes it easier for remote attackers to bypass repoze.who authentication via a forged authorization cookie, a related issue to CVE-2010-3852.","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":"Auth bypass in n/a","id":"CVE-2009-5014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2009"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2009-5015"},"packages":[],"prev":{"headline":"Uncontrolled Resource Consumption in pyftpdlib","id":"CVE-2009-5013"},"products":["n/a"],"published":"2010-11-05","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2009-5015","kev_date_added":null,"published":"2010-11-05"}],"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-09-16","vendors":["n/a"]},"summary":"Remote attackers can bypass authentication in TurboGears2 by forging authorization cookies due to a weak default salt.","url":"https://insights.sbomify.com/CVE-2009-5014/"}