CVE-2020-9075
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 · uneditedHuawei products Secospace USG6300;USG6300E with versions of V500R001C30,V500R001C50,V500R001C60,V500R001C80,V500R005C00,V500R005C10;V600R006C00 have a vulnerability of insufficient input verification. An attacker with limited privilege can exploit this vulnerability to access a specific directory. Successful exploitation of this vulnerability may lead to information leakage.
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 is a path traversal vulnerability caused by insufficient input validation in Huawei USG6300/6300E security appliances. An authenticated attacker with limited privileges can manipulate input to access directories outside the intended scope, leading to information leakage.
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= v500r005c00= v500r005c10= v500r001c30= v500r001c50= v500r001c60= v500r001c80= v600r006c00CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the Huawei USG appliance modelAccess the device console, web interface, or CLI and retrieve the product model information using commands such as 'display device' or by checking the system information page.Affected if The device model is USG6300, USG6300E, or USG6600.
-
Check the installed firmware versionRetrieve the firmware version via CLI command 'display version' or through the web interface system information panel. Compare the version number against the affected ranges.Affected if The firmware version is v500r005c00, v500r005c10, v500r001c30, v500r001c50, v500r001c60, v500r001c80, or v600r006c00.
-
Verify if web management interface is accessibleAttempt to access the device web interface on the configured management port (typically 443 or 8443). Confirm the service is enabled via CLI command 'display http server' or 'display https server'.Affected if The web management interface is enabled and reachable on the network.
-
Confirm authenticated access to the deviceVerify that user accounts with limited privileges exist on the device. Check user accounts via 'display local-user' or by reviewing the AAA configuration.Affected if There are user accounts configured with any privilege level who could potentially exploit the path traversal.
The device is affected if it is a USG6300, USG6300E, or USG6600 model running any of the listed firmware versions (v500r005c00, v500r005c10, v500r001c30, v500r001c50, v500r001c60, v500r001c80, or v600r006c00) and has its web management interface accessible to authenticated users.
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 Huawei patches for the affected versions (V500R001C30 through V600R006C00) or upgrade to a patched version. Implement strict input validation to prevent directory traversal characters in user-supplied paths.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9075 — 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-9075 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