{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2229 exists.","fix":"No fix has been published for CVE-2005-2229 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-2229 is a high-severity vulnerability in n/a, published on 12 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2005-2229 and fix it if it is affected.\n\nWhat it is: CVE-2005-2229 is a high-severity vulnerability in n/a, published on 12 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2229 exists.\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-2229/ (Markdown: https://insights.sbomify.com/CVE-2005-2229/index.md)","id":"CVE-2005-2229","markdown":"https://insights.sbomify.com/CVE-2005-2229/index.md","name":"CVE-2005-2229","record":{"aliases":["GHSA-qp8q-fp29-hx6f"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Blog Torrent","requires_auth":"none","summary":"Remote attackers can access sensitive files containing account names and password hashes stored in web-accessible directories.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"blog_torrent","vendor":"blog_torrent"}],"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":[],"description":"Blog Torrent 0.92 and earlier stores sensitive files under the web document root in the (1) data or (2) torrents directories with insufficient access control, which allows remote attackers to obtain sensitive information such as account names and password hashes, as demonstrated using data/newusers.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-07-11","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-07-11","kind":"exploitdb","ref":"1097","stars":null,"title":"BlogTorrent 0.92 - Remote Password Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2005-2229","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":3,"next":{"headline":"Other in n/a","id":"CVE-2005-2230"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-2228"},"products":["n/a"],"published":"2005-07-12","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Remote attackers can access sensitive files containing account names and password hashes stored in web-accessible directories.","url":"https://insights.sbomify.com/CVE-2005-2229/"}