# CVE-2017-11120: Memory corruption in n/a

> An attacker can trigger a buffer overflow in Broadcom Wi-Fi firmware via malformed RRM frames, potentially leading to code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g3j7-grgr-pgxq

## What is CVE-2017-11120?

CVE-2017-11120 is a critical memory corruption vulnerability in Apple Iphone Os, published on 27 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Broadcom BCM4355C0 Wi-Fi chips 9.44.78.27.0.1.56 and other chips, an attacker can craft a malformed RRM neighbor report frame to trigger an internal buffer overflow in the Wi-Fi firmware, aka B-V2017061204.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-11120?

It affects 3 products.


Products: Apple Iphone Os, Apple Tvos, Broadcom Bcm4355c0 Firmware.

## How do I fix CVE-2017-11120?

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

## Is CVE-2017-11120 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11120 exists.

Public exploit code:

- Apple iOS 10.2 - Broadcom Out-of-Bounds Write when Handling 802.11k Neighbor Report Response (exploitdb)

## Other vulnerabilities in Apple Iphone Os

- [CVE-2021-30666](https://insights.sbomify.com/CVE-2021-30666/): Apple iOS WebKit Buffer Overflow (high 8.8, exploited in the wild)
- [CVE-2021-30761](https://insights.sbomify.com/CVE-2021-30761/): Apple iOS WebKit Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2021-30762](https://insights.sbomify.com/CVE-2021-30762/): Apple iOS WebKit Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2016-4657](https://insights.sbomify.com/CVE-2016-4657/): Apple iOS Webkit Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2019-7286](https://insights.sbomify.com/CVE-2019-7286/): Apple Multiple Products Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11120 and fix it if it is affected.

What it is: CVE-2017-11120 is a critical memory corruption vulnerability in Apple Iphone Os, published on 27 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11120 exists.

Affected product: Apple Iphone Os. 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-2017-11120/ (Markdown: https://insights.sbomify.com/CVE-2017-11120/index.md)
```

## Sources

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

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