CVE-2016-11060
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis vulnerability involves insecure TLS/SSL renegotiation in NETGEAR firewall and router devices (SRX5308, FVS336Gv3, FVS318N, FVS318Gv2). The flaw allows a man-in-the-middle attacker to inject malicious content into an established encrypted SSL/TLS session by intercepting and manipulating the renegotiation process, potentially compromising session integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2017-02-10< 2017-02-10< 2017-02-10< 2017-02-10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the NETGEAR device modelAccess the device admin interface or check the device label to confirm the exact model number. Affected models are: FVS318Gv2, FVS318N, FVS336Gv3, and SRX5308.Affected if The device model is one of FVS318Gv2, FVS318N, FVS336Gv3, or SRX5308.
-
Determine the installed firmware versionLog into the device web management interface and navigate to the Status or Administration section to view the firmware version. Alternatively, check the device backup configuration file for version information.Affected if The firmware version cannot be determined or is older than the 2017-02-10 release date.
-
Compare firmware version to the affected rangeLocate the firmware version displayed in the device status page and note the build date. The vulnerability affects versions released before 2017-02-10.Affected if The firmware version was released before February 10, 2017.
-
Verify if SSL/TLS management access is enabledIn the device web interface, navigate to Administration or Remote Management settings and check whether HTTPS/SSL admin access is enabled. Look for options such as 'Enable HTTPS Admin' or 'Web GUI Access' set to HTTPS.Affected if SSL/TLS management access is enabled on the device.
-
Assess network exposure of management interfaceReview firewall rules or access control lists to determine if the device management interface (port 443/HTTPS) is reachable from untrusted networks such as the public internet or guest network segments.Affected if The SSL/TLS management interface is accessible from untrusted or external networks.
A user is affected if they own one of the affected NETGEAR models (FVS318Gv2, FVS318N, FVS336Gv3, SRX5308) running firmware released before February 10, 2017, with SSL/TLS management enabled and exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2017-02-10
Update firmware on affected NETGEAR devices to versions released on or after 2017-02-10. If immediate patching is not feasible, restrict network access to the device management interfaces and ensure SSL/TLS services are not exposed to untrusted networks.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-11060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data