CVE-2020-1855
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 HEGE-570 version 1.0.1.22(SP3); and HEGE-560, OSCA-550, OSCA-550A, OSCA-550AX, and OSCA-550X version 1.0.1.21(SP3) have an insufficient verification vulnerability. An attacker can access the device physically and exploit this vulnerability to tamper with device information. Successful exploit may cause service abnormal.
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 · low confidenceThis vulnerability in Huawei HEGE-570 (v1.0.1.22SP3) and OSCA-550 series devices (v1.0.1.21SP3) involves insufficient verification of device information, allowing a physically present attacker to tamper with configuration or device data. The physical attack vector and lack of verification integrity enables modification that can disrupt normal device operation.
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.0.1.21\(sp3\)= 1.0.1.21\(sp3\)= 1.0.1.21\(sp3\)= 1.0.1.21\(sp3\)= 1.0.1.21\(sp3\)= 1.0.1.22\(sp3\)CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 device modelLocate the Huawei device in your environment and confirm it is one of the following models: Hege 560, Hege 570, Osca 550, Osca 550a, Osca 550ax, or Osca 550x. Check the device label, management interface, or console output for the exact model designation.Affected if The device is a Huawei Hege 560, Hege 570, Osca 550, 550a, 550ax, or 550x series device.
-
Determine installed firmware versionAccess the device management interface, command line, or system information page and retrieve the firmware version. For Hege 570 look for version 1.0.1.22(sp3), for Hege 560 and Osca 550 series look for version 1.0.1.21(sp3).Affected if The installed firmware version is exactly 1.0.1.22(sp3) for Hege 570, or exactly 1.0.1.21(sp3) for Hege 560 or Osca 550 series.
-
Confirm physical access exposureAssess whether the device is located in an area with unrestricted physical access, such as unlocked rooms, shared racks, or public areas where unauthorized individuals could physically interact with the device.Affected if The device can be physically accessed by persons other than trusted administrators.
-
Check for configuration integrity verificationReview device settings or audit logs to determine whether cryptographic verification or integrity checks of configuration and firmware are enabled or configured.Affected if No cryptographic verification of device configuration or firmware integrity is implemented or configured.
You are affected if you have a Huawei Hege 560, Hege 570, or Osca 550 series device running firmware version 1.0.1.21(sp3) or 1.0.1.22(sp3) with physical accessibility and no integrity verification in place.
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 dataPrimary mitigation involves restricting physical access to affected devices and implementing cryptographic verification of device configuration and firmware to detect tampering. Vendor firmware updates should be applied when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1855 — 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-1855 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