VDB-221845 · CVE-2023-23108 · EUVD-2023-27208

crasm 1.8-3 Xasc null pointer dereference

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.
5.4	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in crasm 1.8-3. This affects the function Xasc. This manipulation causes null pointer dereference. This vulnerability is registered as CVE-2023-23108. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability has been found in crasm 1.8-3 and classified as problematic. Affected by this vulnerability is the function Xasc. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:

In crasm 1.8-3, invalid input validation, specific files passed to the command line application, can lead to a NULL pointer dereference in the function Xasc.

The weakness was published 02/27/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2023-23108 since 01/11/2023. Technical details are known, but no exploit is available.

Applying a patch 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-27208). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

crasm

Version

1.8-3

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

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

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔍

Patch: github.com

Timelineinfo

01/11/2023 🔍
02/27/2023 +47 days 🔍
02/27/2023 +0 days 🔍
10/06/2025 +952 days 🔍

Sourcesinfo

Advisory: github.com
Status: Confirmed

CVE: CVE-2023-23108 (🔍)
GCVE (CVE): GCVE-0-2023-23108
GCVE (VulDB): GCVE-100-221845
EUVD: 🔍

Entryinfo

Created: 02/27/2023 17:25
Updated: 10/06/2025 09:59
Changes: 02/27/2023 17:25 (39), 03/25/2023 14:35 (11), 10/06/2025 09:59 (16)
Complete: 🔍
Cache ID: 216::103

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