# CVE-2024-20671: Microsoft Defender Security Feature Bypass Vulnerability

> Attackers can bypass Microsoft Defender security features, potentially allowing malicious code to evade detection on Windows systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2024
- **Updated:** 3 May 2025
- **Also known as:** GHSA-vp94-mx6w-4h86

## What is CVE-2024-20671?

CVE-2024-20671 is a medium-severity vulnerability in Microsoft Windows Defender Antimalware Platform, published on 12 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Microsoft Defender Security Feature Bypass Vulnerability

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-20671?

It affects 1 product.


Products: Microsoft Windows Defender Antimalware Platform.

## How do I fix CVE-2024-20671?

No fix has been published for CVE-2024-20671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-20671 being exploited?

There is no known exploitation of CVE-2024-20671 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20671 and fix it if it is affected.

What it is: CVE-2024-20671 is a medium-severity vulnerability in Microsoft Windows Defender Antimalware Platform, published on 12 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20671 in the wild and no public exploit code.

Affected product: Microsoft Windows Defender Antimalware Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-20671/ (Markdown: https://insights.sbomify.com/CVE-2024-20671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20671
- OSV: https://osv.dev/vulnerability/CVE-2024-20671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-20671/
Summaries are generated and may contain mistakes; the official description above is the record.