OpenCRX 5.2.2 Request 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.
8.5$0-$5k0.00

Summaryinfo

A vulnerability was found in OpenCRX 5.2.2. It has been rated as critical. The affected element is an unknown function of the component Request Handler. Performing a manipulation results in an unknown weakness. This vulnerability is identified as CVE-2023-46502. The attack can be initiated remotely. There is not any exploit available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in OpenCRX 5.2.2. It has been classified as critical. This affects an unknown function of the component Request Handler. 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. The summary by CVE is:

An issue in OpenCRX v.5.2.2 allows a remote attacker to execute arbitrary code via a crafted request.

The weakness was released 10/31/2023 as ce7a71db0bb34ecbcb0e822d40598e410a48b399. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-46502 since 10/23/2023. Neither technical details nor an exploit are publicly available.

Applying the patch ce7a71db0bb34ecbcb0e822d40598e410a48b399 is able to eliminate this problem. The bugfix is ready for download at github.com.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-2792). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.6
VulDB Meta Temp Score: 8.5

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

NVD Base Score: 9.8
NVD Vector: 🔍

CNA Base Score: 9.8
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: Patch
Status: 🔍

0-Day Time: 🔍

Patch: ce7a71db0bb34ecbcb0e822d40598e410a48b399

Timelineinfo

10/23/2023 🔍
10/31/2023 +8 days 🔍
10/31/2023 +0 days 🔍
10/14/2025 +714 days 🔍

Sourcesinfo

Product: github.com

Advisory: ce7a71db0bb34ecbcb0e822d40598e410a48b399
Status: Confirmed

CVE: CVE-2023-46502 (🔍)
GCVE (CVE): GCVE-0-2023-46502
GCVE (VulDB): GCVE-100-244041
EUVD: 🔍

Entryinfo

Created: 10/31/2023 08:06
Updated: 10/14/2025 17:01
Changes: 10/31/2023 08:06 (39), 11/24/2023 12:47 (12), 09/10/2024 02:00 (26), 10/14/2025 17:01 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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!