{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2005-4346 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2005-4346 yet. Limit exposure of the affected software until one is available.","what":"CVE-2005-4346 is a medium-severity vulnerability in n/a, published on 18 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-4346 and fix it if it is affected.\n\nWhat it is: CVE-2005-4346 is a medium-severity vulnerability in n/a, published on 18 Dec 2005. 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-2005-4346 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-4346/ (Markdown: https://insights.sbomify.com/CVE-2005-4346/index.md)","id":"CVE-2005-4346","markdown":"https://insights.sbomify.com/CVE-2005-4346/index.md","name":"CVE-2005-4346","record":{"aliases":["GHSA-7jrf-mjm4-267q"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"phpBB Blog plugin","requires_auth":"none","summary":"Remote attackers can obtain the full application path via an invalid permalink parameter in phpBB Blog, leading to information disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"phpbb_blog","vendor":"anthony_boyd"}],"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":"Invalid SQL syntax error in blog.php in phpBB Blog 2.2.2 and earlier allows remote attackers to obtain the full path of the application via an invalid permalink parameter to index.php, which produces an invalid SQL query that leaks the full pathname in a SQL syntax error message. NOTE: this was originally claimed to be SQL injection, but a cleansing step strips all non-digit characters and leaves an empty permalink argument, which leads to the syntax error.","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":"Information disclosure in n/a","id":"CVE-2005-4346","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2005"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2005-4347"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2005-4345"},"products":["n/a"],"published":"2005-12-18","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":"Remote attackers can obtain the full application path via an invalid permalink parameter in phpBB Blog, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2005-4346/"}