Skip to content
Fencer Intel
high 7.5

CVE-2010-4254 in the critical feed json

Mono, when Moonlight before 2.3.0.1 or 2.99.x before 2.99.0.10 is used, does not properly validate arguments to generic methods, which allo…

published 15y ago modified 4mo ago also EUVD-2010-4227

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
13.6%
EPSS 13.6% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Mono, when Moonlight before 2.3.0.1 or 2.99.x before 2.99.0.10 is used, does not properly validate arguments to generic methods, which allows remote attackers to bypass generic constraints, and possibly execute arbitrary code, via a crafted method call.

Patch / fix

Is CVE-2010-4254 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-4254 updated cvss 7.5

mono: vulnerability when Moonlight is used may allow arbitrary code execution

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

Timeline

  1. Published
  2. First public exploit (EDB-15974)

Exploit prediction

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

Exploits and checks

  • EDB-15974 Mono/Moonlight Generic Type Argument - Privilege Escalation dos, 2011-01-11

CVSS scores

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

Classification

Weakness
  • CWE-20 Improper Input Validation

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.