| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Netgear WAC120, WAC505, WAC510, WNAP320, WNAP210v2, WNDAP350, WNDAP360, WNDAP660, WNDAP620, WND930 and WN604 and classified as problematic. This impacts an unknown function. Performing a manipulation results in cross-site request forgery. This vulnerability is known as CVE-2018-21120. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.
Details
A vulnerability was found in Netgear WAC120, WAC505, WAC510, WNAP320, WNAP210v2, WNDAP350, WNDAP360, WNDAP660, WNDAP620, WND930 and WN604 (Wireless LAN Software). It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:
Certain NETGEAR devices are affected by CSRF. This affects WAC120 before 2.1.7, WAC505 before 5.0.5.4, WAC510 before 5.0.5.4, WNAP320 before 3.7.11.4, WNAP210v2 before 3.7.11.4, WNDAP350 before 3.7.11.4, WNDAP360 before 3.7.11.4, WNDAP660 before 3.7.11.4, WNDAP620 before 2.1.7, WND930 before 2.1.5, and WN604 before 3.3.10.
The weakness was published 04/22/2020 (Website). The advisory is shared at kb.netgear.com. This vulnerability is uniquely identified as CVE-2018-21120 since 04/20/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.1.7 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.netgear.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.2
NVD Vector: 🔍
CNA Base Score: 5.2
CNA Vector (MITRE): 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WAC120/WAC505/WAC510/WNAP320/WNAP210v2/WNDAP350/WNDAP360/WNDAP660/WNDAP620/WND930/WN604 2.1.7
Timeline
04/20/2020 🔍04/22/2020 🔍
04/23/2020 🔍
05/06/2025 🔍
Sources
Vendor: netgear.comAdvisory: kb.netgear.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-21120 (🔍)
GCVE (CVE): GCVE-0-2018-21120
GCVE (VulDB): GCVE-100-154185
Entry
Created: 04/23/2020 09:37Updated: 05/06/2025 15:44
Changes: 04/23/2020 09:37 (37), 04/23/2020 09:42 (12), 10/11/2020 09:35 (1), 10/11/2020 09:42 (1), 06/01/2024 14:04 (33), 05/06/2025 15:44 (5)
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.