CVE-2011-0989: Medium severity moonlight vulnerability
It was reported [1] that threads in Mono were not properly cleaned up upon finalization, so if one thread was resurrected, it would be possible to see the pointer to freed memory. This could lead to unintended information disclosure, and possibly a crash.
This has been corrected upstream [2].
[1] https://bugzilla.novell.com/showbug.cgi?id=678515 [2] https://github.com/mono/mono/commit/722f9890f09aadfc37ae479e7d946d5fc5ef7b91
Other sources
The RuntimeHelpers.InitializeArray method in metadata/icall.c in Mono, when Moonlight 2.x before 2.4.1 or 3.x before 3.99.3 is used, does not properly restrict data types, which allows remote attackers to modify internal read-only data structures, and cause a denial of service (plugin crash) or corrupt the internal state of the security manager, via a crafted media file, as demonstrated by modifying a C# struct.
— MITRE
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2011-0989?
CVE-2011-0989 has a severity level that indicates potential for information disclosure and system crashes.
How do I fix CVE-2011-0989?
To remediate CVE-2011-0989, upgrade to the latest version of Mono or Novell Moonlight that includes the fix.
What types of software are affected by CVE-2011-0989?
CVE-2011-0989 affects multiple versions of Mono and Novell Moonlight, specifically versions such as 2.0, 2.3.0, 2.4, 2.31, 3.0, and 3.99.
What potential impact does CVE-2011-0989 have on my system?
CVE-2011-0989 can lead to unintended information disclosure and may cause a crash if a thread is resurrected.
Is there a patch available for CVE-2011-0989?
Yes, a patch for CVE-2011-0989 has been made available in the upstream releases.