# CVE-2024-45555: Integer Overflow to Buffer Overflow in Automotive OS Platform

> An integer overflow allows buffer overflow, enabling attackers to bypass boot verification and inject unauthorized code into security-sensitive system images.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-wmhm-48vh-qjwg

## What is CVE-2024-45555?

CVE-2024-45555 is a high-severity vulnerability in Qualcomm Msm8996au Firmware, published on 6 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-787 (Out-of-bounds Write)

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

It affects 41 products.


Products: Qualcomm Msm8996au Firmware, Qualcomm Qam8255p Firmware, Qualcomm Qam8295p Firmware, Qualcomm Qam8620p Firmware, Qualcomm Qam8650p Firmware, Qualcomm Qam8775p Firmware, Qualcomm Qamsrv1h Firmware, Qualcomm Qamsrv1m Firmware, Qualcomm Qca6564a Firmware, Qualcomm Qca6564au Firmware, Qualcomm Qca6574a Firmware, Qualcomm Qca6574au Firmware, Qualcomm Qca6584au Firmware, Qualcomm Qca6595 Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6688aq Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca6698aq Firmware, Qualcomm Sa6145p Firmware, Qualcomm Sa6150p Firmware and 21 more.

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

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

## Is CVE-2024-45555 being exploited?

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

## Other vulnerabilities in Qualcomm Msm8996au Firmware

- [CVE-2017-18318](https://insights.sbomify.com/CVE-2017-18318/): Security feature bypass in Snapdragon Automobile, Snapdragon Mobile (critical 9.8)
- [CVE-2022-33282](https://insights.sbomify.com/CVE-2022-33282/): Integer overflow to buffer overflow in Automotive Multimedia (high 8.4)
- [CVE-2022-25680](https://insights.sbomify.com/CVE-2022-25680/): Memory corruption in Snapdragon Auto (high 8.4)
- [CVE-2024-53030](https://insights.sbomify.com/CVE-2024-53030/): Improper Input Validation in Automotive OS Platform (high 7.8)
- [CVE-2019-2277](https://insights.sbomify.com/CVE-2019-2277/): Memory corruption in Snapdragon Auto, Snapdragon Compute, Snapdragon Consumer IOT, Snapdragon Industrial IOT, Snapdragon Mobile, Snapdragon Voice & Music (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45555 is a high-severity vulnerability in Qualcomm Msm8996au Firmware, published on 6 Jan 2025. 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-45555 in the wild and no public exploit code.

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

## Sources

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

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