CVE-2014-4122
First published: Wed Oct 15 2014(Updated: )
Microsoft .NET Framework 2.0 SP2, 3.5, and 3.5.1 omits the ASLR protection mechanism, which allows remote attackers to obtain potentially sensitive information about memory addresses by leveraging the predictability of an executable image's location, aka ".NET ASLR Vulnerability."
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft .NET Framework 4 | =2.0-sp2 | |
| Microsoft .NET Framework 4 | =3.5 | |
| Microsoft .NET Framework 4 | =3.5.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2014-4122?
CVE-2014-4122 is considered a moderate severity vulnerability due to its potential for information disclosure.
How do I fix CVE-2014-4122?
To fix CVE-2014-4122, it's recommended to upgrade to a later version of the Microsoft .NET Framework that incorporates the ASLR protection mechanism.
What systems are affected by CVE-2014-4122?
CVE-2014-4122 affects Microsoft .NET Framework versions 2.0 SP2, 3.5, and 3.5.1.
What type of vulnerability is CVE-2014-4122?
CVE-2014-4122 is an ASLR (Address Space Layout Randomization) vulnerability that can lead to information disclosure.
Can CVE-2014-4122 be exploited remotely?
Yes, CVE-2014-4122 can be exploited by remote attackers to gain sensitive information about memory addresses.
- agent/references
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/type
- agent/severity
- agent/weakness
- agent/author
- agent/description
- agent/event
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/microsoft
- canonical/microsoft .net framework 4
- version/microsoft .net framework 4/2.0-sp2
- version/microsoft .net framework 4/3.5
- version/microsoft .net framework 4/3.5.1