CVE-2021-22310: There is an information leakage vulnerability in some huawei products.
Noroxi assessment
Priority: Monitor (action score 17/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.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- 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 an information leakage vulnerability in some huawei products. Due to the properly storage of specific information in the log file, the attacker can obtain the information when a user logs in to the device. Successful exploit may cause an information leak. Affected product versions include: NIP6300 versions V500R001C00,V500R001C20,V500R001C30;NIP6600 versions V500R001C00,V500R001C20,V500R001C30;Secospace USG6300 versions V500R001C00,V500R001C20,V500R001C30;Secospace USG6500 versions V500R001C00,V500R001C20,V500R001C30;Secospace USG6600 versions V500R001C00,V500R001C20,V500R001C30,V500R001C50,V500R001C60,V500R001C80;USG9500 versions V500R005C00,V500R005C10.
- Published
- Mar 22, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- CWE-532
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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 | nip6300 firmware | cpe:2.3:o:huawei:nip6300_firmware |
| huawei | nip6300 | cpe:2.3:h:huawei:nip6300 |
| huawei | nip6600 firmware | cpe:2.3:o:huawei:nip6600_firmware |
| huawei | nip6600 | cpe:2.3:h:huawei:nip6600 |
| 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 |
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 NIP6300;NIP6600;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG9500
- V500R001C00,V500R001C20,V500R001C30, V500R001C00,V500R001C20,V500R001C30,V500R001C50,V500R001C60,V500R001C80, V500R005C00,V500R005C10affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei nip6300 firmwarev500r001c00
- huawei nip6300 firmwarev500r001c20
- huawei nip6300 firmwarev500r001c30
- huawei nip6600 firmwarev500r001c00
- huawei nip6600 firmwarev500r001c20
- huawei nip6600 firmwarev500r001c30
- huawei secospace usg6300 firmwarev500r001c00
- huawei secospace usg6300 firmwarev500r001c20
- huawei secospace usg6300 firmwarev500r001c30
- huawei secospace usg6500 firmwarev500r001c00
- huawei secospace usg6500 firmwarev500r001c20
- huawei secospace usg6500 firmwarev500r001c30
- huawei secospace usg6600 firmwarev500r001c00
- huawei secospace usg6600 firmwarev500r001c20
- huawei secospace usg6600 firmwarev500r001c30
- huawei secospace usg6600 firmwarev500r001c50
- huawei secospace usg6600 firmwarev500r001c60
- huawei secospace usg6600 firmwarev500r001c80
- huawei usg9500 firmwarev500r005c00
- huawei usg9500 firmwarev500r005c10
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-1847There is a denial of service vulnerability in some Huawei products.30Monitor
- CVE-2020-9127Some Huawei products have a command injection vulnerability.26Monitor
- CVE-2017-15315Patch module of Huawei NIP6300 V500R001C20SPC100, V500R001C20SPC200, NIP6600 V500R001C20SPC100, V500R001C20SPC200, Secospace USG6300…26Monitor
Published before and after this one in the same product
- Later →CVE-2021-22321Mar 22, 2021 · There is a use-after-free vulnerability in a Huawei product.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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0262 · Mar 23, 2021(Huawei Güvenlik Zafiyeti)
- TR-21-0104 · Feb 4, 2021(Huawei Güvenlik Zafiyeti)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-532 · Insertion of Sensitive Information into Log FileCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/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)
ATT&CK techniques
—
Change log (0)
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.