What is the CVSS score of CVE-2013-0509?

CVE-2013-0509 has a CVSS 2.0 base score of 7.6 (High). CVSS vector: AV:N/AC:H/Au:N/C:C/I:C/A:C. EPSS exploitation probability: 21.7%.

Tivoli Netcool Application Service Monitors CVE-2013-0509

HIGH

Buffer Overflow (CWE-119)

2013-06-05 psirt@us.ibm.com

Buffer Overflow RCE IBM Tivoli Netcool Application Service Monitors Tivoli Netcool System Service Monitors

7.6

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

7.6 HIGH

AV:N/AC:H/Au:N/C:C/I:C/A:C

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:H/Au:N/C:C/I:C/A:C

Attack Vector

Network

Attack Complexity

High

Confidentiality

Integrity

Availability

Lifecycle Timeline

CVE Published

Jun 05, 2013 - 03:43 cve.org

HIGH 7.6

DescriptionCVE.org

Buffer overflow in the Transaction MIB agent in IBM Tivoli Netcool System Service Monitors (SSM) and Application Service Monitors (ASM) 4.0.0 before FP14 allows remote attackers to execute arbitrary code via a SQL transaction with a long table name that is not properly handled by a packet decoder.

AnalysisAI

Buffer overflow in the Transaction MIB agent in IBM Tivoli Netcool System Service Monitors (SSM) and Application Service Monitors (ASM) 4.0.0 before FP14 allows remote attackers to execute arbitrary. Rated high severity (CVSS 7.6), this vulnerability is remotely exploitable. Epss exploitation probability 21.7% and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Buffer Overflow (CWE-119), which allows attackers to corrupt memory to execute arbitrary code or crash the application. Buffer overflow in the Transaction MIB agent in IBM Tivoli Netcool System Service Monitors (SSM) and Application Service Monitors (ASM) 4.0.0 before FP14 allows remote attackers to execute arbitrary code via a SQL transaction with a long table name that is not properly handled by a packet decoder. Affected products include: Ibm Tivoli Netcool Application Service Monitors, Ibm Tivoli Netcool System Service Monitors.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use memory-safe languages or bounds-checking. Enable ASLR, DEP/NX, stack canaries. Use safe string functions.