CVE-2020-1789
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 OSCA-550, OSCA-550A, OSCA-550AX, and OSCA-550X products with version 1.0.1.21(SP3) have an insufficient authentication vulnerability. The software does not require a strong credential when the user trying to do certain operations. Successful exploit could allow an attacker to pass the authentication and do certain operations by a weak credential.
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 confidenceHuawei OSCA-550 series products (OSCA-550, OSCA-550A, OSCA-550AX, OSCA-550X) running version 1.0.1.21(SP3) contain an insufficient authentication vulnerability where the software does not enforce strong credential requirements for certain operations. An attacker with knowledge of weak credentials can bypass authentication and perform unauthorized operations.
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\)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 the OSCA device modelLog into the device management interface or check the physical device label to determine if the model is OSCA-550, OSCA-550A, OSCA-550AX, or OSCA-550XAffected if The device model is any of these four variants (OSCA-550, OSCA-550A, OSCA-550AX, OSCA-550X)
-
Check the installed firmware versionAccess the device admin panel or use the command line interface (CLI) to query the firmware version. Typically found under System > Device Information or via 'display version' command in CLIAffected if The firmware version is exactly 1.0.1.21(SP3)
-
Verify if default or weak credentials are configuredReview the authentication configuration settings in the device management interface. Check whether default vendor credentials are still in use or if weak/simple passwords are configured for administrative accountsAffected if Default credentials are unchanged or weak password policies are applied to user accounts
-
Determine if remote management or API endpoints are exposedCheck network configuration to see if the web management interface, API, or administrative ports (HTTP/HTTPS) are accessible from untrusted networksAffected if Administrative interfaces are reachable from external or untrusted network segments without VPN or IP restrictions
You are affected if you have an OSCA-550 series device running firmware version 1.0.1.21(SP3) with default credentials or weak authentication configured and accessible.
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-provided patches or updates that enforce stronger authentication policies. Until patched, restrict network access to affected devices and monitor for unauthorized access using weak credentials.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1789 — 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-1789 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