{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4371 exists.","fix":"No fix has been published for CVE-2005-4371 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4371 is a medium-severity vulnerability in n/a, published on 20 Dec 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-4371 and fix it if it is affected.\n\nWhat it is: CVE-2005-4371 is a medium-severity vulnerability in n/a, published on 20 Dec 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-4371 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-4371/ (Markdown: https://insights.sbomify.com/CVE-2005-4371/index.md)","id":"CVE-2005-4371","markdown":"https://insights.sbomify.com/CVE-2005-4371/index.md","name":"CVE-2005-4371","record":{"aliases":["GHSA-9qwh-mr4w-j7m3"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Acidcat web application","requires_auth":"none","summary":"Remote attackers can access the database file directly via the web root, leading to sensitive information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"acidcat","vendor":"acidcat"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Acidcat 2.1.13 and earlier stores the database under the web root with insufficient access control, which allows remote attackers to obtain sensitive information via a request to databases/acidcat.mdb.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2005-12-19","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2005-12-19","kind":"exploitdb","ref":"26874","stars":null,"title":"Acidcat CMS 2.1.13 - 'acidcat.mdb' Remote Information Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2005-4371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2005-4372"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2005-4370"},"products":["n/a"],"published":"2005-12-20","related":[{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2005-4370","kev_date_added":null,"published":"2005-12-20"}],"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 the database file directly via the web root, leading to sensitive information disclosure.","url":"https://insights.sbomify.com/CVE-2005-4371/"}