# CVE-2022-37972: Microsoft Endpoint Configuration Manager Spoofing Vulnerability

> Attackers can exploit a spoofing vulnerability in Microsoft Endpoint Configuration Manager to bypass security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2022
- **Updated:** 11 Mar 2025
- **Also known as:** GHSA-94hf-vcvp-rw54

## What is CVE-2022-37972?

CVE-2022-37972 is a high-severity vulnerability in Microsoft Endpoint Configuration Manager, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft Endpoint Configuration Manager Spoofing Vulnerability

## Which versions are affected by CVE-2022-37972?

It affects 1 product.


Products: Microsoft Endpoint Configuration Manager.

## How do I fix CVE-2022-37972?

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

## Is CVE-2022-37972 being exploited?

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

## Other vulnerabilities in Microsoft Endpoint Configuration Manager

- [CVE-2022-24527](https://insights.sbomify.com/CVE-2022-24527/): Microsoft Endpoint Configuration Manager Elevation of Privilege Vulnerability (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37972 and fix it if it is affected.

What it is: CVE-2022-37972 is a high-severity vulnerability in Microsoft Endpoint Configuration Manager, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-37972 in the wild and no public exploit code.

Affected product: Microsoft Endpoint Configuration Manager. 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-2022-37972/ (Markdown: https://insights.sbomify.com/CVE-2022-37972/index.md)
```

## Sources

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

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