{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-0674 exists.","fix":"No fix has been published for CVE-2009-0674 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-0674 is a medium-severity vulnerability in n/a, published on 22 Feb 2009. 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-0674 and fix it if it is affected.\n\nWhat it is: CVE-2009-0674 is a medium-severity vulnerability in n/a, published on 22 Feb 2009. 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-2009-0674 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-2009-0674/ (Markdown: https://insights.sbomify.com/CVE-2009-0674/index.md)","id":"CVE-2009-0674","markdown":"https://insights.sbomify.com/CVE-2009-0674/index.md","name":"CVE-2009-0674","record":{"aliases":["GHSA-3w86-j9mv-8fpr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"RavenNuke CMS","requires_auth":"none","summary":"Remote attackers can determine local file existence via error messages in RavenNuke when specific PHP settings are enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ravennuke","vendor":"ravenphpscripts"}],"cvss":{"score":6,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"images/captcha.php in Raven Web Services RavenNuke 2.30, when register_globals and display_errors are enabled, allows remote attackers to determine the existence of local files by sending requests with full pathnames in the aFonts array parameter, and then observing the error messages, which differ between existing and nonexistent pathnames.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-02-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-02-16","kind":"exploitdb","ref":"8068","stars":null,"title":"ravennuke 2.3.0 - Multiple Vulnerabilities"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2009-0674","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2009"},"n_packages":0,"n_references":7,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2009-0675"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2009-0673"},"products":["n/a"],"published":"2009-02-22","related":[{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2009-0672","kev_date_added":null,"published":"2009-02-22"},{"cvss_score":6.5,"headline":"Code injection in n/a","id":"CVE-2009-0673","kev_date_added":null,"published":"2009-02-22"},{"cvss_score":6.5,"headline":"Code injection in n/a","id":"CVE-2009-0677","kev_date_added":null,"published":"2009-02-22"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2009-0678","kev_date_added":null,"published":"2009-02-22"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2009-0679","kev_date_added":null,"published":"2009-02-22"}],"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)"},{"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 determine local file existence via error messages in RavenNuke when specific PHP settings are enabled.","url":"https://insights.sbomify.com/CVE-2009-0674/"}