CVE-2016-11057: Certain NETGEAR devices are affected by mishandling of repeated URL calls.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 63.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Certain NETGEAR devices are affected by mishandling of repeated URL calls. This affects JNR1010v2 before 2017-01-06, WNR614 before 2017-01-06, WNR618 before 2017-01-06, JWNR2000v5 before 2017-01-06, WNR2020 before 2017-01-06, JWNR2010v5 before 2017-01-06, WNR1000v4 before 2017-01-06, WNR2020v2 before 2017-01-06, R6220 before 2017-01-06, and WNDR3700v5 before 2017-01-06.
- Published
- Apr 28, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- CWE-287
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| netgear | jnr1010 firmware | cpe:2.3:o:netgear:jnr1010_firmware |
| netgear | jnr1010 | cpe:2.3:h:netgear:jnr1010 |
| netgear | jwnr2000 firmware | cpe:2.3:o:netgear:jwnr2000_firmware |
| netgear | jwnr2000 | cpe:2.3:h:netgear:jwnr2000 |
| netgear | jwnr2010 firmware | cpe:2.3:o:netgear:jwnr2010_firmware |
| netgear | jwnr2010 | cpe:2.3:h:netgear:jwnr2010 |
| netgear | r6220 firmware | cpe:2.3:o:netgear:r6220_firmware |
| netgear | r6220 | cpe:2.3:h:netgear:r6220 |
| netgear | wndr3700 firmware | cpe:2.3:o:netgear:wndr3700_firmware |
| netgear | wndr3700 | cpe:2.3:h:netgear:wndr3700 |
| netgear | wnr1000 firmware | cpe:2.3:o:netgear:wnr1000_firmware |
| netgear | wnr1000 | cpe:2.3:h:netgear:wnr1000 |
and 6 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netgear jnr1010 firmwarebefore 2017-01-06
- netgear jwnr2000 firmwarebefore 2017-01-06
- netgear jwnr2010 firmwarebefore 2017-01-06
- netgear r6220 firmwarebefore 2017-01-06
- netgear wndr3700 firmwarebefore 2017-01-06
- netgear wnr1000 firmwarebefore 2017-01-06
- netgear wnr2020 firmwarebefore 2017-01-06
- netgear wnr614 firmwarebefore 2017-01-06
- netgear wnr618 firmwarebefore 2017-01-06
Same product
netgear: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-11014NETGEAR JNR1010 devices before 1.0.0.32 have Incorrect Access Control because the ok value of the auth cookie is a special case.40Plan
- CVE-2017-18737Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.36Monitor
- CVE-2017-18734Certain NETGEAR devices are affected by command injection by an unauthenticated attacker.36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2017-18749Apr 23, 2020 · Certain NETGEAR devices are affected by CSRF.35Monitor
- ← EarlierCVE-2018-21209Apr 28, 2020 · Certain NETGEAR devices are affected by reflected XSS.19Monitor
- Later →CVE-2018-21226Apr 28, 2020 · Certain NETGEAR devices are affected by authentication bypass.35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.