CVE-2021-22356: There is a weak secure algorithm vulnerability in Huawei products.
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
There is a weak secure algorithm vulnerability in Huawei products. A weak secure algorithm is used in a module. Attackers can exploit this vulnerability by capturing and analyzing the messages between devices to obtain information. This can lead to information leak.Affected product versions include: IPS Module V500R005C00SPC100, V500R005C00SPC200; NGFW Module V500R005C00SPC100, V500R005C00SPC200; Secospace USG6300 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; Secospace USG6500 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; Secospace USG6600 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200; USG9500 V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, V500R005C00SPC100, V500R005C00SPC200.
- Published
- Nov 23, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-327
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| huawei | ips module firmware | cpe:2.3:o:huawei:ips_module_firmware |
| huawei | ips module | cpe:2.3:h:huawei:ips_module |
| huawei | ngfw module firmware | cpe:2.3:o:huawei:ngfw_module_firmware |
| huawei | ngfw module | cpe:2.3:h:huawei:ngfw_module |
| huawei | secospace usg6300 firmware | cpe:2.3:o:huawei:secospace_usg6300_firmware |
| huawei | secospace usg6300 | cpe:2.3:h:huawei:secospace_usg6300 |
| huawei | secospace usg6500 firmware | cpe:2.3:o:huawei:secospace_usg6500_firmware |
| huawei | secospace usg6500 | cpe:2.3:h:huawei:secospace_usg6500 |
| huawei | secospace usg6600 firmware | cpe:2.3:o:huawei:secospace_usg6600_firmware |
| huawei | secospace usg6600 | cpe:2.3:h:huawei:secospace_usg6600 |
| huawei | usg9500 firmware | cpe:2.3:o:huawei:usg9500_firmware |
| huawei | usg9500 | cpe:2.3:h:huawei:usg9500 |
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei ips module firmwarev500r005c00spc100
- huawei ips module firmwarev500r005c00spc200
- huawei ngfw module firmwarev500r005c00spc100
- huawei ngfw module firmwarev500r005c00spc200
- huawei secospace usg6300 firmwarev500r001c30spc200
- huawei secospace usg6300 firmwarev500r001c30spc600
- huawei secospace usg6300 firmwarev500r001c60spc500
- huawei secospace usg6300 firmwarev500r005c00spc100
- huawei secospace usg6300 firmwarev500r005c00spc200
- huawei secospace usg6500 firmwarev500r001c30spc200
- huawei secospace usg6500 firmwarev500r001c30spc600
- huawei secospace usg6500 firmwarev500r001c60spc500
- huawei secospace usg6500 firmwarev500r005c00spc100
- huawei secospace usg6500 firmwarev500r005c00spc200
- huawei secospace usg6600 firmwarev500r001c30spc200
- huawei secospace usg6600 firmwarev500r001c30spc600
- huawei secospace usg6600 firmwarev500r001c60spc500
- huawei secospace usg6600 firmwarev500r005c00spc100
- huawei secospace usg6600 firmwarev500r005c00spc200
- huawei usg9500 firmwarev500r001c30spc200
Versions reported by the vendor
Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.
n/a IPS Module;NGFW Module;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500
- V500R005C00SPC100,V500R005C00SPC200, V500R001C30SPC200,V500R001C30SPC600,V500R001C60SPC500,V500R005C00SPC100,V500R005C00SPC200affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-9099Huawei products IPS Module; NGFW Module; NIP6300; NIP6600; NIP6800; Secospace USG6300; Secospace USG6500; Secospace USG6600; USG9500 with ve39Monitor
- CVE-2021-37129There is an out of bounds write vulnerability in some Huawei products.30Monitor
- CVE-2021-22320There is a denial of service vulnerability in Huawei products.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-22342Jun 22, 2021 · There is an information leak vulnerability in Huawei products.19Monitor
- ← EarlierCVE-2021-22341Jun 29, 2021 · There is a memory leak vulnerability in Huawei products.19Monitor
- Later →CVE-2020-1818Dec 27, 2024 · There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some 21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0940 · Nov 24, 2021(Huawei Güvenlik Zafiyeti)
- TR-21-0912 · Nov 11, 2021(Huawei Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-327 · Use of a Broken or Risky Cryptographic AlgorithmCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Creating a Rogue Certification Authority CertificateCAPEC-459likelihood: Medium · Very High
- Signature SpoofCAPEC-473
- Signature Spoofing by Improper ValidationCAPEC-475likelihood: Low · High
- Cryptanalysis of Cellular EncryptionCAPEC-608High
- Rooting SIM CardsCAPEC-614High
- CryptanalysisCAPEC-97likelihood: Low · Very High
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.