Heap-buffer-overflow in libucl: ucl_hash_destroy

libucl Updated 02 Oct 2025

Summary

17/10/2023
MEDIUM
No i
Medium
Not published

OSV-2023-1025: Heap-buffer-overflow in ucl_hash_destroy. Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

libucl is an open-source library that provides a parser and an object model for handling Universal Configuration Language (UCL) data. It is commonly used for parsing and manipulating configuration files in various applications. However, a vulnerability has been discovered in the library that can lead to a heap-buffer-overflow.

Vulnerability Detail

The vulnerability in libucl, specifically in the function ucl_hash_destroy, allows for a heap-buffer-overflow read of 8 bytes. This can result in a crash and potentially be exploited by an attacker to execute arbitrary code or cause a denial-of-service condition. The vulnerability has been reported through the OSS-Fuzz project and further details can be found in the provided link.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, developers can implement bounds checking and input validation in their applications to mitigate the risk of exploitation. By ensuring that input data is properly validated and not exceeding the expected bounds, the impact of the vulnerability can be reduced.

Conclusion

In conclusion, libucl is vulnerable to a heap-buffer-overflow in the ucl_hash_destroy function. This vulnerability can have serious security implications, including potential code execution or denial-of-service. It is crucial for developers to update their applications to the latest version of libucl that includes the fix for this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libucl →

Share this vulnerability

FAQ

libucl is an open-source library for parsing and manipulating Universal Configuration Language (UCL) data. It is commonly used in applications that require configuration file handling.

A heap-buffer-overflow is a type of vulnerability where a program attempts to read or write data outside the bounds of a heap-allocated buffer. This can lead to crashes, memory corruption, and potential code execution.

An attacker can exploit this vulnerability by providing specially crafted input that triggers the heap-buffer-overflow. This can potentially allow the attacker to execute arbitrary code or cause a denial-of-service condition.

Yes, the maintainers of libucl have addressed this vulnerability and released a fixed version. It is recommended to update to the latest version of libucl to mitigate the risk.

There are no known instances of this vulnerability being actively exploited in the wild. However, it is important to apply the necessary updates and security measures to protect against potential exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for libucl.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback