# CVE-2016-10319: Integer overflow in n/a

> Integer overflow in ARM Trusted Firmware allows copying large data into secure memory, potentially enabling code execution or privilege escalation.

- **Severity:** Medium 5.9 (`CVSS:3.0/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:** No
- **Published:** 6 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vc9m-4w2w-692j

## What is CVE-2016-10319?

CVE-2016-10319 is a medium-severity vulnerability in n/a, published on 6 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In ARM Trusted Firmware 1.2 and 1.3, a malformed firmware update SMC can result in copying unexpectedly large data into secure memory because of integer overflows. This affects certain cases involving execution of both AArch64 Generic Trusted Firmware (TF) BL1 code and other firmware update code.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2016-10319?

It affects 1 product.


Products: Arm Trusted Firmware Project Arm Trusted Firmware.

## How do I fix CVE-2016-10319?

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

## Is CVE-2016-10319 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10319 and fix it if it is affected.

What it is: CVE-2016-10319 is a medium-severity vulnerability in n/a, published on 6 Apr 2017. 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-2016-10319 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-2016-10319/ (Markdown: https://insights.sbomify.com/CVE-2016-10319/index.md)
```

## Sources

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

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