NEC Aterm WF1200CR/Aterm WG1200CR/Aterm WG2600HS URL integrity check
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in NEC Aterm WF1200CR, Aterm WG1200CR and Aterm WG2600HS. This issue affects some unknown processing of the component URL Handler. This manipulation causes integrity check. This vulnerability is handled as CVE-2021-20709. There is not any exploit available.
Details
A vulnerability classified as problematic was found in NEC Aterm WF1200CR, Aterm WG1200CR and Aterm WG2600HS (affected version unknown). Affected by this vulnerability is an unknown functionality of the component URL Handler. The manipulation with an unknown input leads to a integrity check vulnerability. The CWE definition for the vulnerability is CWE-354. The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 04/26/2021. The advisory is shared at jvn.jp. This vulnerability is known as CVE-2021-20709. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Integrity checkCWE: CWE-354 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/17/2020 🔍04/26/2021 🔍
04/26/2021 🔍
04/29/2021 🔍
Sources
Advisory: jvn.jpStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2021-20709 (🔍)
GCVE (CVE): GCVE-0-2021-20709
GCVE (VulDB): GCVE-100-173881
Entry
Created: 04/26/2021 08:31Updated: 04/29/2021 15:00
Changes: 04/26/2021 08:31 (35), 04/29/2021 15:00 (2)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.