GPAC up to 2.2.1 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.
6.1$0-$5k0.00

Summaryinfo

A vulnerability described as problematic has been identified in GPAC up to 2.2.1. Affected is an unknown function. The manipulation results in null pointer dereference. This vulnerability was named CVE-2023-2840. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in GPAC up to 2.2.1. It has been classified as problematic. Affected is an unknown code block. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. CVE summarizes:

NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.2.2.

The weakness was presented 05/22/2023. The advisory is shared for download at huntr.dev. This vulnerability is traded as CVE-2023-2840 since 05/22/2023. There are neither technical details nor an exploit publicly available.

Upgrading to version 2.2.2 eliminates this vulnerability. Applying the patch ba59206b3225f0e8e95a27eff41cb1c49ddf9a37 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-34291). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 6.1

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CNA Base Score: 5.3
CNA Vector (huntr.dev): 🔍

CVSSv2info

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

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

Exploitinginfo

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

Physical: Partially
Local: Yes
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: GPAC 2.2.2
Patch: ba59206b3225f0e8e95a27eff41cb1c49ddf9a37

Timelineinfo

05/22/2023 🔍
05/22/2023 +0 days 🔍
05/22/2023 +0 days 🔍
12/19/2025 +942 days 🔍

Sourcesinfo

Product: github.com

Advisory: ba59206b3225f0e8e95a27eff41cb1c49ddf9a37
Status: Confirmed

CVE: CVE-2023-2840 (🔍)
GCVE (CVE): GCVE-0-2023-2840
GCVE (VulDB): GCVE-100-229668
EUVD: 🔍

Entryinfo

Created: 05/22/2023 22:38
Updated: 12/19/2025 01:39
Changes: 05/22/2023 22:38 (50), 06/16/2023 08:13 (1), 06/16/2023 08:15 (11), 12/19/2025 01:39 (17)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!