# CVE-2024-38425: Improper Authorization in Performance

> An attacker can access application launch information via implicit broadcasts, leading to information disclosure on Qualcomm Snapdragon devices.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **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:** 7 Oct 2024
- **Updated:** 7 Oct 2024
- **Also known as:** GHSA-2v26-h6g3-vrgj

## What is CVE-2024-38425?

CVE-2024-38425 is a medium-severity vulnerability in Qualcomm Fastconnect 6900 Firmware, published on 7 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Information disclosure while sending implicit broadcast containing APP launch information.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

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

It affects 24 products.


Products: Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Sm7435 Firmware, Qualcomm Sm8635 Firmware, Qualcomm Sm8750 Firmware, Qualcomm Snapdragon 480\+ 5g Mobile Platform \(Sm4350-Ac\) Firmware, Qualcomm Snapdragon 480 5g Mobile Platform Firmware, Qualcomm Snapdragon 4 Gen 1 Mobile Platform Firmware, Qualcomm Snapdragon 4 Gen 2 Mobile Platform Firmware, Qualcomm Snapdragon 662 Mobile Platform Firmware, Qualcomm Snapdragon 680 4g Mobile Platform Firmware, Qualcomm Snapdragon 685 4g Mobile Platform \(Sm6225-Ad\) Firmware, Qualcomm Snapdragon 695 5g Mobile Platform Firmware, Qualcomm Snapdragon 6 Gen 1 Mobile Platform Firmware, Qualcomm Snapdragon 7\+ Gen 2 Mobile Platform Firmware, Qualcomm Snapdragon 7 Gen 1 Mobile Platform Firmware, Qualcomm Snapdragon 8\+ Gen 1 Mobile Platform Firmware, Qualcomm Snapdragon 8\+ Gen 2 Mobile Platform Firmware, Qualcomm Snapdragon 8 Gen 1 Mobile Platform Firmware, Qualcomm Snapdragon 8 Gen 2 Mobile Platform Firmware and 4 more.

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

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

## Is CVE-2024-38425 being exploited?

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

## Other vulnerabilities in Qualcomm Fastconnect 6900 Firmware

- [CVE-2024-38399](https://insights.sbomify.com/CVE-2024-38399/): Use After Free in Graphics (high 8.4)
- [CVE-2024-21472](https://insights.sbomify.com/CVE-2024-21472/): Use After Free in Kernel (high 8.4)
- [CVE-2025-47405](https://insights.sbomify.com/CVE-2025-47405/): Untrusted Pointer Dereference in Camera (high 7.8)
- [CVE-2025-47358](https://insights.sbomify.com/CVE-2025-47358/): Use After Free in Secure Processor (high 7.8)
- [CVE-2025-47350](https://insights.sbomify.com/CVE-2025-47350/): Use After Free in DSP Service (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38425 is a medium-severity vulnerability in Qualcomm Fastconnect 6900 Firmware, published on 7 Oct 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-38425 in the wild and no public exploit code.

Affected product: Qualcomm Fastconnect 6900 Firmware. 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-38425/ (Markdown: https://insights.sbomify.com/CVE-2024-38425/index.md)
```

## Sources

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

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