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>
Affected Software | Affected Version | How to fix |
---|---|---|
Mono |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-694933 is considered moderate due to the potential for information disclosure and possible crashes.
To fix REDHAT-BUG-694933, update your Mono package to the latest version that includes the upstream fix.
The impact of REDHAT-BUG-694933 includes the risk of unintended information disclosure and application crashes.
REDHAT-BUG-694933 affects the Mono framework.
There is no specific workaround for REDHAT-BUG-694933; the recommended action is to apply the software update.