CVE-2020-1847: There is a denial of service vulnerability in some Huawei products.
Noroxi assessment
Priority: Monitor (action score 30/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.74% (FIRST EPSS); higher than 54.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is 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 1 time 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 denial of service vulnerability in some Huawei products. There is no protection against the attack scenario of specific protocol. A remote, unauthorized attackers can construct attack scenarios, which leads to denial of service.Affected product versions include:NIP6300 versions V500R001C30,V500R001C60;NIP6600 versions V500R001C30,V500R001C60;Secospace USG6300 versions V500R001C30,V500R001C60;Secospace USG6500 versions V500R001C30,V500R001C60;Secospace USG6600 versions V500R001C30,V500R001C60;USG9500 versions V500R001C30,V500R001C60.
- Published
- Nov 13, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
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 | 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei nip6300 firmwarev500r001c30
- huawei nip6300 firmwarev500r001c60
- huawei nip6600 firmwarev500r001c30
- huawei nip6600 firmwarev500r001c60
- huawei secospace usg6300 firmwarev500r001c30
- huawei secospace usg6300 firmwarev500r001c60
- huawei secospace usg6500 firmwarev500r001c30
- huawei secospace usg6500 firmwarev500r001c60
- huawei secospace usg6600 firmwarev500r001c30
- huawei secospace usg6600 firmwarev500r001c60
- huawei usg9500 firmwarev500r001c30
- huawei usg9500 firmwarev500r001c60
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
- V500R001C30,V500R001C60affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- 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 V500R0026Monitor
- CVE-2021-22321There is a use-after-free vulnerability in a Huawei product.21Monitor
Published before and after this one in the same product
- Later →CVE-2021-22310Mar 22, 2021 · There is an information leakage vulnerability in some huawei products.17Monitor
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-20-960 · Nov 13, 2020(Huawei Ürünleri için Güvenlik Güncellemesi Yayınladı)
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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.