CVE-2020-1843
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-560 version 1.0.1.20(SP2), OSCA-550 version 1.0.0.71(SP1), OSCA-550A version 1.0.0.71(SP1), OSCA-550AX version 1.0.0.71(SP2), and OSCA-550X version 1.0.0.71(SP2) have an insufficient verification vulnerability. An attacker can perform specific operations to exploit this vulnerability by physical access methods. Successful exploitation may cause the attacker perform an illegal operation.
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 confidenceInsufficient verification vulnerability in Huawei HEGE-560 and OSCA-550 series devices allowing attackers with physical access to perform unauthorized operations. The vulnerability stems from inadequate authentication or authorization checks that can be bypassed through physical interaction with the affected devices.
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.20\(sp2\)= 1.0.0.71\(sp1\)= 1.0.0.71\(sp1\)= 1.0.0.71\(sp2\)= 1.0.0.71\(sp2\)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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/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 modelPhysically inspect the device or check system documentation to confirm the exact model number (Huawei Hege 560, Osca 550, Osca 550a, Osca 550ax, or Osca 550x)Affected if Device is one of the Huawei HEGE-560 or OSCA-550 series models listed in the affected products
-
Check installed firmware versionAccess the device firmware settings or system information interface to retrieve the current firmware version number and service pack level (sp1 or sp2)Affected if Firmware version cannot be determined or the device does not provide version information through standard interfaces
-
Compare firmware version against affected listMatch your installed firmware version to the affected versions: Hege 560 = 1.0.1.20(sp2), Osca 550 = 1.0.0.71(sp1), Osca 550a = 1.0.0.71(sp1), Osca 550ax = 1.0.0.71(sp2), Osca 550x = 1.0.0.71(sp2)Affected if The installed firmware version exactly matches one of the listed affected versions (exact version match with sp1 or sp2)
-
Verify physical access controlsAssess whether the device is located in an area with controlled physical access, since this vulnerability requires attackers to have physical access to the deviceAffected if The device is in a location with unrestricted physical access
You are affected if your device is a Huawei HEGE-560 or OSCA-550 series running the exact firmware versions specified (1.0.1.20 sp2 for Hege 560, or 1.0.0.71 sp1/sp2 for Osca variants) and the device has insufficient physical access 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 dataRestrict physical access to affected devices and implement additional physical security controls. Contact Huawei for patched firmware versions addressing this insufficient verification vulnerability.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1843 — 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-1843 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