{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4311 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-4311 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-4311 is a high-severity code injection vulnerability in IBM Tivoli Monitoring, published on 23 Apr 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-4311 and fix it if it is affected.\n\nWhat it is: CVE-2020-4311 is a high-severity code injection vulnerability in IBM Tivoli Monitoring, published on 23 Apr 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-4311 in the wild and no public exploit code.\n\nAffected product: IBM Tivoli Monitoring. 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-4311/ (Markdown: https://insights.sbomify.com/CVE-2020-4311/index.md)","id":"CVE-2020-4311","markdown":"https://insights.sbomify.com/CVE-2020-4311/index.md","name":"CVE-2020-4311","record":{"aliases":["GHSA-rv3f-x6rg-3mm8"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IBM Tivoli Monitoring","requires_auth":"none","summary":"A local attacker can execute arbitrary code by placing a crafted file that triggers DLL loading, affecting IBM Tivoli Monitoring.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"tivoli_monitoring","vendor":"ibm"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/S:U/UI:N/A:H/C:H/I:H/PR:N/AC:H/E:U/RL:O/RC:C","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"IBM Tivoli Monitoring 6.3.0 could allow a local attacker to execute arbitrary code on the system. By placing a specially crafted file, an attacker could exploit this vulnerability to load other DLL files located in the same directory and execute arbitrary code on the system. IBM X-Force ID: 177083.","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":"Code injection in Tivoli Monitoring","id":"CVE-2020-4311","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in Sterling B2B Integrator","id":"CVE-2020-4312"},"packages":[],"prev":{"headline":"Denial of service in MQ","id":"CVE-2020-4310"},"products":["Tivoli Monitoring"],"published":"2020-04-23","related":[{"cvss_score":9.9,"headline":"Privilege escalation in n/a","id":"CVE-2015-7411","kev_date_added":null,"published":"2016-03-12"},{"cvss_score":9.8,"headline":"IBM Tivoli Monitoring code execution","id":"CVE-2025-3357","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":9.8,"headline":"Code injection in Tivoli Monitoring V6","id":"CVE-2017-1789","kev_date_added":null,"published":"2018-03-22"},{"cvss_score":8.6,"headline":"IBM Tivoli Monitoring is vulnerable to unauthenticated file read and write operations","id":"CVE-2025-3356","kev_date_added":null,"published":"2025-10-30"},{"cvss_score":8.5,"headline":"Command injection in n/a","id":"CVE-2015-5003","kev_date_added":null,"published":"2016-01-03"},{"cvss_score":8.5,"headline":"Privilege escalation in n/a","id":"CVE-2014-6141","kev_date_added":null,"published":"2015-02-02"},{"cvss_score":8.1,"headline":"IBM Tivoli Monitoring code execution","id":"CVE-2025-3320","kev_date_added":null,"published":"2025-08-06"}],"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 execute arbitrary code by placing a crafted file that triggers DLL loading, affecting IBM Tivoli Monitoring.","url":"https://insights.sbomify.com/CVE-2020-4311/"}