What is the CVSS score of CVE-2012-1584?

CVE-2012-1584 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:N/A:P. EPSS exploitation probability: 2.8%.

Is there a public PoC exploit available for CVE-2012-1584?

Yes, a public proof-of-concept exploit is available for CVE-2012-1584. Prioritise patching immediately. EPSS: 2.8%.

Is there a patch available for CVE-2012-1584?

Yes, a patch is available for CVE-2012-1584. Update the affected software to the latest version immediately.

Taglib CVE-2012-1584

MEDIUM

Numeric Errors (CWE-189)

2012-09-06 secalert@redhat.com

Denial Of Service Taglib

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:M/Au:N/C:N/I:N/A:P

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:N/I:N/A:P

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

None

Availability

Lifecycle Timeline

CVE Published

Sep 06, 2012 - 18:55 cve.org

MEDIUM 4.3

DescriptionCVE.org

Integer overflow in the mid function in toolkit/tbytevector.cpp in TagLib 1.7 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a crafted file header field in a media file, which triggers a large memory allocation.

AnalysisAI

Integer overflow in the mid function in toolkit/tbytevector.cpp in TagLib 1.7 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a crafted file header. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable. Public exploit code available.

Technical ContextAI

This vulnerability is classified under CWE-189. Integer overflow in the mid function in toolkit/tbytevector.cpp in TagLib 1.7 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a crafted file header field in a media file, which triggers a large memory allocation. Affected products include: Scott Wheeler Taglib.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.