cwlviewer up to 1.3.0 SnakeYaml Constructor deserialization

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.
7.5$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in cwlviewer up to 1.3.0. This impacts an unknown function of the component SnakeYaml Constructor Handler. This manipulation causes deserialization. The identification of this vulnerability is CVE-2021-41110. The attack needs to be done within the local network. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in cwlviewer up to 1.3.0. Affected by this vulnerability is an unknown functionality of the component SnakeYaml Constructor Handler. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was shared 10/02/2021 as GHSA-7g7j-f5g3-fqp7. The advisory is shared at github.com. This vulnerability is known as CVE-2021-41110 since 09/15/2021. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.3.1 eliminates this vulnerability. Applying the patch f6066f09edb70033a2ce80200e9fa9e70a5c29de is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

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

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.7
VulDB Meta Temp Score: 7.5

VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 9.1
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Deserialization
CWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: cwlviewer 1.3.1
Patch: f6066f09edb70033a2ce80200e9fa9e70a5c29de

Timelineinfo

09/15/2021 🔍
10/02/2021 +17 days 🔍
10/02/2021 +0 days 🔍
10/08/2021 +6 days 🔍

Sourcesinfo

Advisory: GHSA-7g7j-f5g3-fqp7
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-41110 (🔍)
GCVE (CVE): GCVE-0-2021-41110
GCVE (VulDB): GCVE-100-183709

Entryinfo

Created: 10/02/2021 08:10
Updated: 10/08/2021 10:46
Changes: 10/02/2021 08:10 (51), 10/08/2021 10:46 (2)
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 ▸

Interested in the pricing of exploits?

See the underground prices here!