codehaus-plexus prior 3.0.24 xml external entity reference

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

Summaryinfo

A vulnerability was found in codehaus-plexus and classified as problematic. This issue affects some unknown processing. The manipulation results in xml external entity reference. This vulnerability was named CVE-2022-4245. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in codehaus-plexus. It has been classified as problematic. Affected is an unknown code. The manipulation with an unknown input leads to a xml external entity reference vulnerability. CWE is classifying the issue as CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

A flaw was found in codehaus-plexus. The org.codehaus.plexus.util.xml.XmlWriterUtil#writeComment fails to sanitize comments for a --> sequence. This issue means that text contained in the command string could be interpreted as XML and allow for XML injection.

The weakness was presented 05/31/2023 as SNYK-JAVA-ORGCODEHAUSPLEXUS-461102. The advisory is shared for download at security.snyk.io. This vulnerability is traded as CVE-2022-4245 since 12/01/2022. There are neither technical details nor an exploit publicly available.

Upgrading to version 3.0.24 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.7
VulDB Meta Temp Score: 4.6

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.3
NVD Vector: 🔍

CNA Base Score: 4.3
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Xml external entity reference
CWE: CWE-611 / CWE-610
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: codehaus-plexus 3.0.24

Timelineinfo

12/01/2022 🔍
05/31/2023 +180 days 🔍
05/31/2023 +0 days 🔍
10/10/2024 +498 days 🔍

Sourcesinfo

Advisory: SNYK-JAVA-ORGCODEHAUSPLEXUS-461102
Status: Confirmed

CVE: CVE-2022-4245 (🔍)
GCVE (CVE): GCVE-0-2022-4245
GCVE (VulDB): GCVE-100-230388

Entryinfo

Created: 05/31/2023 18:12
Updated: 10/10/2024 23:04
Changes: 05/31/2023 18:12 (37), 10/10/2024 23:04 (36)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!