CVE-2020-27873
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 · uneditedThis vulnerability allows network-adjacent attackers to disclose sensitive information on affected installations of NETGEAR R7450 1.2.0.62_1.0.1 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the SOAP API endpoint, which listens on TCP port 80 by default. The issue results from the lack of proper access control. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-11559.
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 in NETGEAR R7450 routers (firmware 1.2.0.62_1.0.1) allows unauthenticated network-adjacent attackers to retrieve stored credentials via the unprotected SOAP API endpoint on TCP port 80. The lack of proper access control on the SOAP service enables direct credential disclosure without any authentication, potentially giving attackers administrative access to the device.
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< 1.2.0.76< 1.2.0.76< 1.2.0.76< 1.2.0.76< 1.2.0.76< 1.2.0.76< 1.2.0.76< 1.2.0.76CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 router modelLocate the model number on the device label or router admin interface (typically at 192.168.1.1)Affected if Model is R7450, Ac2100, Ac2400, Ac2600, R6700, R6800, R6900, R7200, or R7350
-
Check firmware versionAccess router admin interface and navigate to Firmware Update or Administration section to view current firmware versionAffected if Firmware version is below 1.2.0.76
-
Verify SOAP service accessibilityScan TCP port 80 on the router's public IP or internal IP using nmap (nmap -p 80 <router_ip>) or curl to confirm HTTP service is listeningAffected if HTTP service on port 80 is exposed and accessible
-
Test SOAP endpoint for authentication requirementSend an HTTP POST request to the SOAP API endpoint (typically /soap/server.php or /ctl/IGD) with a probe payload to see if it accepts requests without authenticationAffected if SOAP endpoint responds without requiring any authentication credentials
You are affected if you own any of the listed Netgear router models running firmware version 1.2.0.76 or lower, and the SOAP service on TCP port 80 is accessible without authentication.
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 data1.2.0.76
Apply the NETGEAR firmware update when available. As a temporary workaround, disable the SOAP/UPnP service if accessible, and restrict network access to the router's management interface.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27873 — 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-2020-27873 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