{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-1906 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-1906 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-1906 is a medium-severity memory corruption vulnerability in Ibm Db2, published on 3 Jun 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-1906 and fix it if it is affected.\n\nWhat it is: CVE-2009-1906 is a medium-severity memory corruption vulnerability in Ibm Db2, published on 3 Jun 2009. 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-2009-1906 in the wild and no public exploit code.\n\nAffected product: Ibm Db2. 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-1906/ (Markdown: https://insights.sbomify.com/CVE-2009-1906/index.md)","id":"CVE-2009-1906","markdown":"https://insights.sbomify.com/CVE-2009-1906/index.md","name":"CVE-2009-1906","record":{"aliases":["GHSA-rhx4-qcjj-rcmx"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM DB2 database","requires_auth":"none","summary":"Remote attackers can crash IBM DB2 via a malformed IPv6 address in the APPID string, causing denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"db2","vendor":"ibm"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"The DRDA Services component in IBM DB2 9.1 before FP7 and 9.5 before FP4 allows remote attackers to cause a denial of service (memory corruption and application crash) via an IPv6 address in the correlation token in the APPID string, as demonstrated by an APPID string sent by the third-party DataDirect JDBC driver 3.7.32.","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":"Memory corruption in n/a","id":"CVE-2009-1906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:db2","products":["ibm:db2"],"type":"memory_corruption","year":"2009"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2009-1907"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2009-1905"},"products":["n/a"],"published":"2009-06-03","related":[{"cvss_score":10,"headline":"IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors.","id":"CVE-2012-1797","kev_date_added":null,"published":"2012-03-20"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2010-3731","kev_date_added":null,"published":"2010-10-05"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2010-3193","kev_date_added":null,"published":"2010-08-31"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2009-4335","kev_date_added":null,"published":"2009-12-16"},{"cvss_score":10,"headline":"Missing authorization in n/a","id":"CVE-2009-3473","kev_date_added":null,"published":"2009-09-29"},{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2008-6820","kev_date_added":null,"published":"2009-06-03"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-6821","kev_date_added":null,"published":"2009-06-03"}],"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-09-16","vendors":["n/a"]},"summary":"Remote attackers can crash IBM DB2 via a malformed IPv6 address in the APPID string, causing denial of service.","url":"https://insights.sbomify.com/CVE-2009-1906/"}