Skip to content
Fencer Vulns
critical 9.3

CVE-2009-4257 json

Heap-based buffer overflow in datatype/smil/common/smlpkt.cpp in smlrender.dll in RealNetworks RealPlayer 10, RealPlayer 10.5 6.0.12.1040 t…

published 2010-01-25 16 y ago modified 2026-06-16 4 mo ago also EUVD-2009-4226

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.5%
EPSS 8.5% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Heap-based buffer overflow in datatype/smil/common/smlpkt.cpp in smlrender.dll in RealNetworks RealPlayer 10, RealPlayer 10.5 6.0.12.1040 through 6.0.12.1741, RealPlayer 11 11.0.0 through 11.0.4, RealPlayer Enterprise, Mac RealPlayer 10 and 10.1, Linux RealPlayer 10 and 11.0.0, and Helix Player 10.x and 11.0.0 allows remote attackers to execute arbitrary code via an SMIL file with crafted string lengths.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-4257 updated cvss 6.8

RealPlayer: SMIL getAtom heap buffer overflow

  • Red Hat Enterprise Linux AS version 4 HelixPlayer 1.0.6-1.el4_8.1 Red Hat Enterprise Linux Desktop version 4 HelixPlayer 1.0.6-1.el4_8.1 Red Hat Enterprise Linux ES version 4 HelixPlayer 1.0.6-1.el4_8.1 Red Hat Enterprise Linux WS version 4 HelixPlayer 1.0.6-1.el4_8.1
    fixed: vendor fix RHSA-2010:0094

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

8.49% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.