{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4387 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4387 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4387 is a medium-severity vulnerability in Ibm Db2, published on 1 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-4387 and fix it if it is affected.\n\nWhat it is: CVE-2020-4387 is a medium-severity vulnerability in Ibm Db2, published on 1 Jul 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-4387 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-2020-4387/ (Markdown: https://insights.sbomify.com/CVE-2020-4387/index.md)","id":"CVE-2020-4387","markdown":"https://insights.sbomify.com/CVE-2020-4387/index.md","name":"CVE-2020-4387","record":{"aliases":["GHSA-q795-2wrr-3f96"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM DB2 database","requires_auth":"none","summary":"A local attacker can exploit a symbolic link race condition in IBM DB2 to obtain sensitive information.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"db2","vendor":"ibm"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.0/C:H/UI:N/PR:N/A:N/AC:L/I:N/AV:L/S:U/E:U/RC:C/RL:O","version":"3.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, 11.1, and 11.5 could allow a local user to obtain sensitive information using a race condition of a symbolic link. IBM X-Force ID: 179269.","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":"Race condition in DB2 for Linux- UNIX and Windows","id":"CVE-2020-4387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:db2","products":["ibm:db2"],"type":"race_condition","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in Cognos Analytics","id":"CVE-2020-4388"},"packages":[],"prev":{"headline":"Race condition in DB2 for Linux- UNIX and Windows","id":"CVE-2020-4386"},"products":["DB2 for Linux- UNIX and Windows"],"published":"2020-07-01","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":"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-09-16","vendors":["IBM"]},"summary":"A local attacker can exploit a symbolic link race condition in IBM DB2 to obtain sensitive information.","url":"https://insights.sbomify.com/CVE-2020-4387/"}