First published: Fri Apr 08 2011(Updated: )
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] <a href="https://bugzilla.novell.com/show_bug.cgi?id=678515">https://bugzilla.novell.com/show_bug.cgi?id=678515</a> [2] <a href="https://github.com/mono/mono/commit/722f9890f09aadfc37ae479e7d946d5fc5ef7b91">https://github.com/mono/mono/commit/722f9890f09aadfc37ae479e7d946d5fc5ef7b91</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Novell Moonlight | =3.0 | |
Novell Moonlight | =2.4 | |
Novell Moonlight | =2.31 | |
Novell Moonlight | =3.99 | |
Mono Mono | ||
Novell Moonlight | =2.3.0 | |
Novell Moonlight | =2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.