{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-2606 exists.","fix":"No fix has been published for CVE-2009-2606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-2606 is a medium-severity vulnerability in n/a, published on 27 Jul 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-2606 and fix it if it is affected.\n\nWhat it is: CVE-2009-2606 is a medium-severity vulnerability in n/a, published on 27 Jul 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-2606 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-2606/ (Markdown: https://insights.sbomify.com/CVE-2009-2606/index.md)","id":"CVE-2009-2606","markdown":"https://insights.sbomify.com/CVE-2009-2606/index.md","name":"CVE-2009-2606","record":{"aliases":["GHSA-mwf2-x6q4-2rwj"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Football Pool application","requires_auth":"none","summary":"Remote attackers can download the sensitive database file by directly requesting NFL.mdb due to insufficient access control.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"asp_football_pool","vendor":"brainjar"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"ASP Football Pool 2.3 stores sensitive information under the web root with insufficient access control, which allows remote attackers to download the database file via a direct request for NFL.mdb.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2009-06-01","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2009-06-01","kind":"exploitdb","ref":"8852","stars":null,"title":"ASP Football Pool 2.3 - Remote Database Disclosure"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2009-2606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2009"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2009-2607"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2009-2605"},"products":["n/a"],"published":"2009-07-27","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":"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 download the sensitive database file by directly requesting NFL.mdb due to insufficient access control.","url":"https://insights.sbomify.com/CVE-2009-2606/"}