lloyd yajl 2.1.0 yajl_tree_parse memory leak

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in lloyd yajl 2.1.0. This vulnerability affects the function yajl_tree_parse. Performing a manipulation results in memory leak. This vulnerability is known as CVE-2023-33460. No exploit is available.

Detailsinfo

A vulnerability classified as problematic has been found in lloyd yajl 2.1.0. This affects the function yajl_tree_parse. The manipulation with an unknown input leads to a memory leak vulnerability. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. This is going to have an impact on availability. The summary by CVE is:

There's a memory leak in yajl 2.1.0 with use of yajl_tree_parse function. which will cause out-of-memory in server and cause crash.

The weakness was published 06/06/2023 as 250. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-33460 since 05/22/2023. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 242744 (NewStart CGSL MAIN 7.02 : yajl Vulnerability (NS-SA-2025-0202)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (242744), EUVD (EUVD-2023-37623) and CERT Bund (WID-SEC-2023-2853). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Open Source CentOS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • Gentoo Linux
  • Red Hat OpenShift
  • Meinberg LANTIME

Productinfo

Vendor

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

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

NVD Base Score: 6.5
NVD Vector: 🔍

CNA Base Score: 6.5
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 242744
Nessus Name: NewStart CGSL MAIN 7.02 : yajl Vulnerability (NS-SA-2025-0202)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/22/2023 🔍
06/06/2023 +15 days 🔍
06/06/2023 +0 days 🔍
01/04/2026 +943 days 🔍

Sourcesinfo

Product: github.com

Advisory: 250
Status: Confirmed

CVE: CVE-2023-33460 (🔍)
GCVE (CVE): GCVE-0-2023-33460
GCVE (VulDB): GCVE-100-230805
EUVD: 🔍
CERT Bund: WID-SEC-2023-2853 - Red Hat Enterprise Linux: Mehrere Schwachstellen

Entryinfo

Created: 06/06/2023 15:08
Updated: 01/04/2026 11:30
Changes: 06/06/2023 15:08 (39), 06/30/2023 15:01 (11), 01/08/2025 20:01 (26), 07/26/2025 15:28 (2), 12/31/2025 07:43 (7), 01/04/2026 11:30 (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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!