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

CVE-2012-1904 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: 5.6%.

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

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

Realplayer CVE-2012-1904

MEDIUM

Buffer Overflow (CWE-119)

2012-03-28 cve@mitre.org

Buffer Overflow Denial Of Service Realplayer Realplayer Sp

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

Mar 28, 2012 - 10:55 cve.org

MEDIUM 4.3

DescriptionCVE.org

mp4fformat.dll in the QuickTime File Format plugin in RealNetworks RealPlayer 15 and earlier, and RealPlayer SP 1.1.4 Build 12.0.0.756 and earlier, allows remote attackers to cause a denial of service (memory corruption and application crash) via a crafted MP4 file.

AnalysisAI

mp4fformat.dll in the QuickTime File Format plugin in RealNetworks RealPlayer 15 and earlier, and RealPlayer SP 1.1.4 Build 12.0.0.756 and earlier, allows remote attackers to cause a denial of. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable. Public exploit code available 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. mp4fformat.dll in the QuickTime File Format plugin in RealNetworks RealPlayer 15 and earlier, and RealPlayer SP 1.1.4 Build 12.0.0.756 and earlier, allows remote attackers to cause a denial of service (memory corruption and application crash) via a crafted MP4 file. Affected products include: Realnetworks Realplayer, Realnetworks Realplayer Sp.

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.