DevExpress up to 23.1.2 ASP.NET Web Form 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.
3.2$0-$5k0.00

Summaryinfo

A vulnerability was found in DevExpress up to 23.1.2. It has been classified as problematic. Affected is an unknown function of the component ASP.NET Web Form Handler. The manipulation leads to deserialization. This vulnerability is uniquely identified as CVE-2023-35814. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in DevExpress up to 23.1.2 and classified as problematic. This issue affects an unknown code block of the component ASP.NET Web Form Handler. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is integrity. The summary by CVE is:

DevExpress before 23.1.3 does not properly protect XtraReport serialized data in ASP.NET web forms.

The advisory is shared at supportcenter.devexpress.com. The identification of this vulnerability is CVE-2023-35814 since 06/17/2023. The exploitation is known to be difficult. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.

Upgrading to version 21.2.12, 22.1.7, 22.1.9, 22.2.3, 22.2.6 or 23.1.3 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-39809). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.2

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 3.5
CNA Vector (MITRE): 🔍

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: DevExpress 21.2.12/22.1.7/22.1.9/22.2.3/22.2.6/23.1.3

Timelineinfo

06/17/2023 🔍
04/28/2025 +681 days 🔍
04/28/2025 +0 days 🔍
01/11/2026 +258 days 🔍

Sourcesinfo

Advisory: supportcenter.devexpress.com
Status: Confirmed

CVE: CVE-2023-35814 (🔍)
GCVE (CVE): GCVE-0-2023-35814
GCVE (VulDB): GCVE-100-306437
EUVD: 🔍

Entryinfo

Created: 04/28/2025 21:44
Updated: 01/11/2026 07:49
Changes: 04/28/2025 21:44 (62), 01/11/2026 07:49 (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 ▸

Might our Artificial Intelligence support you?

Check our Alexa App!