# CVE-2016-11060: Security feature bypass in n/a

> Attackers can bypass TLS security features via insecure renegotiation on affected NETGEAR routers, compromising communication integrity.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 28 Apr 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vrcx-5x3x-m79f

## What is CVE-2016-11060?

CVE-2016-11060 is a high-severity vulnerability in n/a, published on 28 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain NETGEAR devices are affected by insecure renegotiation. This affects SRX5308 before 2017-02-10, FVS336Gv3 before 2017-02-10, FVS318N before 2017-02-10, and FVS318Gv2 before 2017-02-10.

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

It affects 4 products.


Products: Netgear Fvs318g Firmware, Netgear Fvs318n Firmware, Netgear Fvs336g Firmware, Netgear Srx5308 Firmware.

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

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

## Is CVE-2016-11060 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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