# CVE-2024-38108: Azure Stack Hub Spoofing Vulnerability


- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Aug 2024
- **Updated:** 10 Jul 2025
- **Also known as:** GHSA-rjjr-f65p-jqf6

## What is CVE-2024-38108?

CVE-2024-38108 is a critical vulnerability in Microsoft Azure Stack Hub, published on 13 Aug 2024. 

### Official description

Azure Stack Hub Spoofing Vulnerability

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Microsoft Azure Stack Hub.

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

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

## Is CVE-2024-38108 being exploited?

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

## Other vulnerabilities in Microsoft Azure Stack Hub

- [CVE-2024-38220](https://insights.sbomify.com/CVE-2024-38220/): Azure Stack Hub Elevation of Privilege Vulnerability (critical 9.0)
- [CVE-2024-38216](https://insights.sbomify.com/CVE-2024-38216/): Azure Stack Hub Elevation of Privilege Vulnerability (high 8.2)
- [CVE-2025-53793](https://insights.sbomify.com/CVE-2025-53793/): Azure Stack Hub Information Disclosure Vulnerability (high 7.5)
- [CVE-2024-38201](https://insights.sbomify.com/CVE-2024-38201/): Azure Stack Hub Elevation of Privilege Vulnerability (high 7.0)
- [CVE-2024-20679](https://insights.sbomify.com/CVE-2024-20679/): Azure Stack Hub Spoofing Vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38108 is a critical vulnerability in Microsoft Azure Stack Hub, published on 13 Aug 2024. 
Exploitation: There is no known exploitation of CVE-2024-38108 in the wild and no public exploit code.

Affected product: Microsoft Azure Stack Hub. 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-38108/ (Markdown: https://insights.sbomify.com/CVE-2024-38108/index.md)
```

## Sources

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

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