Skip to content
Fencer Intel
medium 5.0

CVE-2010-0417 json

Buffer overflow in common/util/rlstate.cpp in Helix Player 1.0.6 and RealPlayer allows remote attackers to cause a denial of service (appli…

published 16y ago modified 4mo ago also EUVD-2010-0448

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

Summary

Buffer overflow in common/util/rlstate.cpp in Helix Player 1.0.6 and RealPlayer allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a RuleBook structure with a large number of rule-separator characters that trigger heap memory corruption.

Patch / fix

  • HelixPlayer RHEL 4 1:1.0.6-1.el4_8.1

red hat advisories RHSA-2010:0094

Is CVE-2010-0417 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2010-0417 updated cvss 6.8

RealPlayer: rule book handling heap corruption

  • 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

4.15% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

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

References

Sources

Fencer Intel 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.