CVE-2020-1860
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 · uneditedNIP6800;Secospace USG6600;USG9500 products with versions of V500R001C30; V500R001C60SPC500; V500R005C00SPC100 have an access control bypass vulnerability. Attackers that can access to the internal network can exploit this vulnerability with careful deployment. Successful exploit may cause the access control to be bypassed, and attackers can directly access the Internet.
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 · moderate confidenceThis is an access control bypass vulnerability in Huawei NIP6800, Secospace USG6600, and USG9500 firewall/UTM products running specific firmware versions (V500R001C30, V500R001C60SPC500, V500R005C00SPC100). Attackers who already have internal network access can exploit this vulnerability to bypass the device's security controls, enabling unauthorized direct Internet access.
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= v500r001c30= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00= v500r001c30= v500r001c60= v500r005c00CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the Huawei firewall modelAccess the device console, web interface, or use 'display device' command to confirm the exact model (NIP6800, USG6600, or USG9500)Affected if The model is NIP6800, Secospace USG6600, or USG9500
-
Check the firmware versionRun 'display version' command on the device console or check the system info page in the web management interfaceAffected if The firmware version is V500R001C30, V500R001C60, or V500R005C00 exactly
-
Verify if internal-to-external access control is configuredCheck security policy rules using 'display security-policy rule all' or review the policy configuration via web interface under Security Policy or Policy settingsAffected if No strict outbound policy exists or the policy can be bypassed allowing unrestricted internet access from internal networks
-
Check for unauthorized active sessions bypassing security controlsUse 'display session all' or 'display firewall session table' to review active connections, particularly those showing direct internal-to-external flowsAffected if Sessions exist showing internal network hosts connecting directly to external IP addresses despite security policy configuration
A user is affected if they have a Huawei NIP6800, USG6600, or USG9500 device running firmware version V500R001C30, V500R001C60, or V500R005C00 where internal users can access the internet directly without going through expected security controls.
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 dataApply vendor-supplied patches for the affected firmware versions. Until patches are available, implement additional network segmentation and egress filtering to restrict unauthorized outbound access.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1860 — 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-1860 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