CVE-2025-3354 Details
Description
IBM Tivoli Monitoring 6.3.0.7 through 6.3.0.7 Service Pack 20 is vulnerable to a heap-based buffer overflow, caused by improper bounds checking. A remote attacker could overflow a buffer and execute arbitrary code on the system or cause the server to crash.
A heap-based buffer overflow vulnerability has been identified in IBM Tivoli Monitoring versions 6.3.0.7 through 6.3.0.7 Service Pack 20. This vulnerability arises from improper bounds checking, allowing remote attackers to overflow a buffer, execute arbitrary code on the system, or cause the server to crash.
Users are advised to upgrade to IBM Tivoli Monitoring version 6.3.0.7-TIV-ITM-SP0021. Instructions for downloading this version are available on the IBM Support page.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Aug 7, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://www.ibm.com/support/pages/node/7241472 | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-122 | Heap-based Buffer Overflow | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| ibm tivoli monitoring | 6.3.0.7 - 6.3.0.7 sp1 6.3.0.7 sp10 6.3.0.7 sp11 6.3.0.7 sp12 6.3.0.7 sp13 6.3.0.7 sp14 6.3.0.7 sp15 6.3.0.7 sp16 6.3.0.7 sp17 6.3.0.7 sp18 6.3.0.7 sp19 6.3.0.7 sp2 6.3.0.7 sp20 6.3.0.7 sp3 6.3.0.7 sp4 6.3.0.7 sp5 6.3.0.7 sp6 6.3.0.7 sp7 6.3.0.7 sp8 6.3.0.7 sp9 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Aug 13, 2025 | Initial Analysis | [email protected] |
| Aug 6, 2025 | New CVE Received | [email protected] |