{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-3357 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3357 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3357 is a critical memory corruption vulnerability in IBM Tivoli Monitoring, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-3357 and fix it if it is affected.\n\nWhat it is: CVE-2025-3357 is a critical memory corruption vulnerability in IBM Tivoli Monitoring, published on 28 May 2025. 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-2025-3357 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-2025-3357/ (Markdown: https://insights.sbomify.com/CVE-2025-3357/index.md)","id":"CVE-2025-3357","markdown":"https://insights.sbomify.com/CVE-2025-3357/index.md","name":"CVE-2025-3357","record":{"aliases":["GHSA-f5w7-cjpw-qq45"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Tivoli Monitoring","requires_auth":"none","summary":"A remote attacker can execute arbitrary code on IBM Tivoli Monitoring due to improper validation of an array index.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"tivoli_monitoring","vendor":"ibm"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-129","name":"Improper Validation of Array Index"},{"id":"CWE-1285","name":"Improper Validation of Specified Index, Position, or Offset in Input"}],"description":"IBM Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 19 could allow a remote attacker to execute arbitrary code due to improper validation of an index value of a dynamically allocated array.","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":"IBM Tivoli Monitoring code execution","id":"CVE-2025-3357","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-3358"},"packages":[],"prev":{"headline":"IBM Tivoli Monitoring is vulnerable to unauthenticated file read and write operations","id":"CVE-2025-3356"},"products":["Tivoli Monitoring"],"published":"2025-05-28","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":"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["IBM"]},"summary":"A remote attacker can execute arbitrary code on IBM Tivoli Monitoring due to improper validation of an array index.","url":"https://insights.sbomify.com/CVE-2025-3357/"}