# CVE-2024-37325: Azure Science Virtual Machine (DSVM) Elevation of Privilege Vulnerability

> Attackers can elevate privileges within Azure Data Science Virtual Machines, requiring users to apply vendor patches.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/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:** 11 Jun 2024
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-8whg-5x3x-gjj9

## What is CVE-2024-37325?

CVE-2024-37325 is a high-severity vulnerability in Microsoft Azure Data Science Virtual Machines, published on 11 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Azure Science Virtual Machine (DSVM) Elevation of Privilege Vulnerability

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Microsoft Azure Data Science Virtual Machine.

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

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

## Is CVE-2024-37325 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37325 is a high-severity vulnerability in Microsoft Azure Data Science Virtual Machines, published on 11 Jun 2024. 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-2024-37325 in the wild and no public exploit code.

Affected product: Microsoft Azure Data Science Virtual Machines. 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-37325/ (Markdown: https://insights.sbomify.com/CVE-2024-37325/index.md)
```

## Sources

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

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