# CVE-2018-16528: Memory corruption in n/a

> Remote attackers can execute arbitrary code on devices using AWS FreeRTOS due to memory corruption in TLS connectivity modules.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x364-mjf7-297c

## What is CVE-2018-16528?

CVE-2018-16528 is a high-severity memory corruption vulnerability in n/a, published on 6 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Amazon Web Services (AWS) FreeRTOS through 1.3.1 allows remote attackers to execute arbitrary code because of mbedTLS context object corruption in prvSetupConnection and GGD_SecureConnect_Connect in AWS TLS connectivity modules.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-16528?

It affects 1 product.


Products: Amazon Amazon Web Services Freertos.

## How do I fix CVE-2018-16528?

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

## Is CVE-2018-16528 being exploited?

There is no known exploitation of CVE-2018-16528 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-16601](https://insights.sbomify.com/CVE-2018-16601/): Integer overflow in n/a (high 8.1)
- [CVE-2019-13120](https://insights.sbomify.com/CVE-2019-13120/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16528 and fix it if it is affected.

What it is: CVE-2018-16528 is a high-severity memory corruption vulnerability in n/a, published on 6 Dec 2018. 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-2018-16528 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-2018-16528/ (Markdown: https://insights.sbomify.com/CVE-2018-16528/index.md)
```

## Sources

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

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