# CVE-2024-31852: Code injection in n/a

> A miscompilation in the LLVM ARM backend can overwrite the LR register, potentially allowing control flow hijacking and code execution.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Apr 2024
- **Updated:** 4 Dec 2024
- **Also known as:** AZL-39713, AZL-39728, AZL-39758, AZL-39776, AZL-39785, AZL-39791, AZL-39830, AZL-39842, AZL-49774, DEBIAN-CVE-2024-31852, ECHO-0dc2-d323-a26e, GHSA-gj98-2c7c-vmc4, UBUNTU-CVE-2024-31852

## What is CVE-2024-31852?

CVE-2024-31852 is a medium-severity code injection vulnerability in n/a, published on 5 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is "we don't have strong objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is most likely to crash on most valid inputs to the function. So, if this function is covered by any testing, the miscompile is most likely to be discovered before the binary is shipped to production."

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


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

Upgrade to a fixed version.

## Is CVE-2024-31852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31852 is a medium-severity code injection vulnerability in n/a, published on 5 Apr 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-31852 in the wild and no public exploit code.

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

## Sources

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

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