CVE-2021-22309
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 · uneditedThere is insecure algorithm vulnerability in Huawei products. A module uses less random input in a secure mechanism. Attackers can exploit this vulnerability by brute forcing to obtain sensitive message. This can lead to information leak. Affected product versions include:USG9500 versions V500R001C30SPC200, V500R001C60SPC500,V500R005C00SPC200;USG9520 versions V500R005C00;USG9560 versions V500R005C00;USG9580 versions V500R005C00.
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 confidenceA module in Huawei USG9500, USG9520, USG9560, and USG9580 firewall products uses insufficient randomness (weak entropy) in a cryptographic security mechanism. Attackers can exploit this by brute-forcing to obtain sensitive messages, leading to information disclosure.
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= v500r001c30spc200= v500r001c60spc500= v500r005c00spc200= v500r005c00= v500r005c00= 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 USG firewall modelLog into the device management interface or use the command line to query the hardware model (e.g., display device-manufacture-info or check the physical device label)Affected if The model is USG9500, USG9520, USG9560, or USG9580
-
Determine the installed firmware versionAccess the device CLI or web management interface and run the command to display the firmware version (e.g., display version or check system info in the web UI)Affected if A version number is returned that can be compared against the affected list
-
Compare firmware version against affected list for USG9500If the model is USG9500, check if the version equals v500r001c30spc200, v500r001c60spc500, or v500r005c00spc200Affected if The installed version matches any of these three versions exactly
-
Compare firmware version against affected list for USG9520/9560/9580If the model is USG9520, USG9560, or USG9580, check if the version equals v500r005c00Affected if The installed version is exactly v500r005c00
The device is affected if it is a USG9500 running firmware v500r001c30spc200, v500r001c60spc500, or v500r005c00spc200, or a USG9520/9560/9580 running firmware v500r005c00.
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 the vendor-supplied patches (V500R001C30SPC200, V500R001C60SPC500, V500R005C00SPC200 for USG9500; V500R005C00 for USG9520/9560/9580). If patches are unavailable, implement compensating controls such as network segmentation and enhanced monitoring around affected devices.
- Consultation3.0 h
- Implementation5.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 $3,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22309 — 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-2021-22309 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