{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-6053 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2007-6053 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-6053 is a critical memory corruption vulnerability in Ibm Db2 Universal Database, published on 20 Nov 2007."},"fix_prompt":"Check this codebase for CVE-2007-6053 and fix it if it is affected.\n\nWhat it is: CVE-2007-6053 is a critical memory corruption vulnerability in Ibm Db2 Universal Database, published on 20 Nov 2007. \nExploitation: There is no known exploitation of CVE-2007-6053 in the wild and no public exploit code.\n\nAffected product: Ibm Db2 Universal Database. 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-2007-6053/ (Markdown: https://insights.sbomify.com/CVE-2007-6053/index.md)","id":"CVE-2007-6053","markdown":"https://insights.sbomify.com/CVE-2007-6053/index.md","name":"CVE-2007-6053","record":{"aliases":["GHSA-qw4x-8f78-c38x"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"IBM DB2 database","requires_auth":"unknown","summary":"IBM DB2 database suffers from memory corruption when handling many file descriptors, with unclear security impact requiring a patch.","user_interaction":"unknown","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"db2_universal_database","vendor":"ibm"}],"cvss":{"score":9.3,"severity":"critical","source":"nvd","vector":"AV:N/AC:M/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-399","name":null}],"description":"IBM DB2 UDB 9.1 before Fixpak 4 does not properly handle use of large numbers of file descriptors, which might allow attackers to have an unknown impact involving \"memory corruption.\" NOTE: the vendor description of this issue is too vague to be certain that it is security-related.","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-2007-6053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:db2_universal_database","products":["ibm:db2_universal_database"],"type":"memory_corruption","year":"2007"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2007-6054"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2007-6052"},"products":["n/a"],"published":"2007-11-20","related":[{"cvss_score":10,"headline":"Unspecified vulnerability in (1) DB2WATCH and (2) DB2FREEZE in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors.","id":"CVE-2007-6045","kev_date_added":null,"published":"2007-11-20"},{"cvss_score":10,"headline":"Command injection in n/a","id":"CVE-2007-6047","kev_date_added":null,"published":"2007-11-20"},{"cvss_score":10,"headline":"Misconfiguration in n/a","id":"CVE-2007-6048","kev_date_added":null,"published":"2007-11-20"},{"cvss_score":10,"headline":"IBM DB2 UDB 9.1 before Fixpak 4 assigns incorrect privileges to the (1) DB2ADMNS and (2) DB2USERS alternative groups, which has unknown impact.","id":"CVE-2007-6051","kev_date_added":null,"published":"2007-11-20"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2005-4865","kev_date_added":null,"published":"2007-10-06"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2005-0417","kev_date_added":null,"published":"2005-02-14"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2008-3853","kev_date_added":null,"published":"2008-08-28"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"IBM DB2 database suffers from memory corruption when handling many file descriptors, with unclear security impact requiring a patch.","url":"https://insights.sbomify.com/CVE-2007-6053/"}