What is the severity of CVE-2014-4062?

CVE-2014-4062 has a Critical severity rating due to its potential for enabling remote code execution.

What software is affected by CVE-2014-4062?

CVE-2014-4062 affects Microsoft .NET Framework versions 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5, and 3.5.1.

How do I fix CVE-2014-4062?

To fix CVE-2014-4062, ensure you apply the latest security updates provided by Microsoft for the affected .NET Framework versions.

What are the potential impacts of CVE-2014-4062?

The potential impacts of CVE-2014-4062 include unauthorized access to sensitive information and possible remote code execution.

When was CVE-2014-4062 discovered?

CVE-2014-4062 was publicly disclosed in July 2014.

Vulnerability/
CVE-2014-4062

medium

4.3

CWE

264

12/8/2014

12/10/2018

CVE-2014-4062

First published: Tue Aug 12 2014(Updated: )

Microsoft .NET Framework 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5, and 3.5.1 does not properly implement the ASLR protection mechanism, which allows remote attackers to obtain sensitive address information via a crafted web site, aka ".NET ASLR Vulnerability."

Credit: secure@microsoft.com

Affected Software	Affected Version	How to fix
Microsoft .NET Framework	=1.1-sp1
Microsoft .NET Framework	=2.0-sp2
Microsoft .NET Framework	=3.0-sp2
Microsoft .NET Framework	=3.5
Microsoft .NET Framework	=3.5.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-4062?
CVE-2014-4062 has a Critical severity rating due to its potential for enabling remote code execution.
What software is affected by CVE-2014-4062?
CVE-2014-4062 affects Microsoft .NET Framework versions 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5, and 3.5.1.
How do I fix CVE-2014-4062?
To fix CVE-2014-4062, ensure you apply the latest security updates provided by Microsoft for the affected .NET Framework versions.
What are the potential impacts of CVE-2014-4062?
The potential impacts of CVE-2014-4062 include unauthorized access to sensitive information and possible remote code execution.
When was CVE-2014-4062 discovered?
CVE-2014-4062 was publicly disclosed in July 2014.

agent/severity
agent/author
agent/type
agent/event
agent/softwarecombine
agent/first-publish-date
agent/last-modified-date
agent/tags
agent/references
agent/description
agent/weakness
collector/nvd-index
agent/software-canonical-lookup-request
vendor/microsoft
canonical/microsoft .net framework
version/microsoft .net framework/1.1-sp1
version/microsoft .net framework/2.0-sp2
version/microsoft .net framework/3.0-sp2
version/microsoft .net framework/3.5
version/microsoft .net framework/3.5.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2014-4062?
CVE-2014-4062 has a Critical severity rating due to its potential for enabling remote code execution.
What software is affected by CVE-2014-4062?
CVE-2014-4062 affects Microsoft .NET Framework versions 1.1 SP1, 2.0 SP2, 3.0 SP2, 3.5, and 3.5.1.
How do I fix CVE-2014-4062?
To fix CVE-2014-4062, ensure you apply the latest security updates provided by Microsoft for the affected .NET Framework versions.
What are the potential impacts of CVE-2014-4062?
The potential impacts of CVE-2014-4062 include unauthorized access to sensitive information and possible remote code execution.
When was CVE-2014-4062 discovered?
CVE-2014-4062 was publicly disclosed in July 2014.