cJSON up to 1.7.17 parse_string cJSON_ParseWithLength out-of-bounds

Summaryinfo

A vulnerability, which was classified as problematic, has been found in cJSON up to 1.7.17. The impacted element is the function cJSON_ParseWithLength of the component parse_string. Performing a manipulation results in out-of-bounds. This vulnerability is known as CVE-2023-53154. Attacking locally is a requirement. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in cJSON up to 1.7.17. This affects the function cJSON_ParseWithLength of the component parse_string. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on availability. The summary by CVE is:

parse_string in cJSON before 1.7.18 has a heap-based buffer over-read via {"1":1, with no trailing newline if cJSON_ParseWithLength is called.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-53154 since 05/23/2025. The exploitability is told to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 238477 (Debian dla-4216 : libcjson-dev - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.7.18 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (238477). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• cJSON

Version

• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3
• 1.7.4
• 1.7.5
• 1.7.6
• 1.7.7
• 1.7.8
• 1.7.9
• 1.7.10
• 1.7.11
• 1.7.12
• 1.7.13
• 1.7.14
• 1.7.15
• 1.7.16
• 1.7.17

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

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

Discussion