Elecom EDWRC-2533GST2 cross-site request forgery

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.9$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Elecom WRC-1167GST2, WRC-1167GST2A, WRC-1167GST2H, WRC-2533GS2-B, WRC-2533GS2-W, WRC-1750GS, WRC-1750GSV, WRC-1900GST, WRC-2533GST, WRC-2533GSTA, WRC-2533GST2, WRC-2533GST2SP, WRC-2533GST2-G and EDWRC-2533GST2. This impacts an unknown function. This manipulation causes cross-site request forgery. This vulnerability is registered as CVE-2021-20862. The attack requires access to the local network. No exploit is available.

Detailsinfo

A vulnerability was found in Elecom WRC-1167GST2, WRC-1167GST2A, WRC-1167GST2H, WRC-2533GS2-B, WRC-2533GS2-W, WRC-1750GS, WRC-1750GSV, WRC-1900GST, WRC-2533GST, WRC-2533GSTA, WRC-2533GST2, WRC-2533GST2SP, WRC-2533GST2-G and EDWRC-2533GST2. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity.

The weakness was published 12/01/2021. The advisory is shared at jvn.jp. This vulnerability is known as CVE-2021-20862 since 12/17/2020. It demands that the victim is doing some kind of user interaction. 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.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.9
VulDB Meta Temp Score: 3.9

VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Cross-site request forgery
CWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

12/17/2020 🔍
12/01/2021 +349 days 🔍
12/01/2021 +0 days 🔍
12/04/2021 +3 days 🔍

Sourcesinfo

Advisory: jvn.jp
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-20862 (🔍)
GCVE (CVE): GCVE-0-2021-20862
GCVE (VulDB): GCVE-100-187405

Entryinfo

Created: 12/01/2021 10:03
Updated: 12/04/2021 21:11
Changes: 12/01/2021 10:03 (36), 12/04/2021 20:56 (1), 12/04/2021 21:03 (18), 12/04/2021 21:11 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!