# CVE-2019-13120: Information disclosure in n/a

> An attacker with MQTT publish authorization can trigger memory leakage in Amazon FreeRTOS by sending malformed packets, exposing arbitrary memory contents.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vvg7-3vpg-wq97

## What is CVE-2019-13120?

CVE-2019-13120 is a high-severity vulnerability in n/a, published on 7 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Amazon FreeRTOS up to and including v1.4.8 lacks length checking in prvProcessReceivedPublish, resulting in untargetable leakage of arbitrary memory contents on a device to an attacker. If an attacker has the authorization to send a malformed MQTT publish packet to an Amazon IoT Thing, which interacts with an associated vulnerable MQTT message in the application, specific circumstances could trigger this vulnerability.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2019-13120?

It affects 1 product.


Products: Amazon Amazon Web Services Freertos.

## How do I fix CVE-2019-13120?

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

## Is CVE-2019-13120 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16522](https://insights.sbomify.com/CVE-2018-16522/): Null dereference in n/a (high 8.1)
- [CVE-2018-16525](https://insights.sbomify.com/CVE-2018-16525/): Memory corruption in n/a (high 8.1)
- [CVE-2018-16526](https://insights.sbomify.com/CVE-2018-16526/): Memory corruption in n/a (high 8.1)
- [CVE-2018-16528](https://insights.sbomify.com/CVE-2018-16528/): Memory corruption in n/a (high 8.1)
- [CVE-2018-16601](https://insights.sbomify.com/CVE-2018-16601/): Integer overflow in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13120 and fix it if it is affected.

What it is: CVE-2019-13120 is a high-severity vulnerability in n/a, published on 7 Oct 2019. 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-2019-13120 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-2019-13120/ (Markdown: https://insights.sbomify.com/CVE-2019-13120/index.md)
```

## Sources

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

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