Segv on unknown address in kh_get_ucl_hash_caseless_node in libucl

libucl Updated 02 Oct 2025

Summary

27/08/2023
N/A
No i
Unrated
Not published

OSV-2023-747: Segv on unknown address in kh_get_ucl_hash_caseless_node. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libucl is an open-source library that provides a parser and an object model for the Universal Configuration Language (UCL). It is commonly used for parsing configuration files in various applications. The library allows developers to read, modify, and generate UCL data structures. However, a vulnerability has been discovered in libucl that can lead to a segmentation fault (segv) when accessing an unknown address in the kh_get_ucl_hash_caseless_node function.

Vulnerability Detail

The vulnerability in libucl arises from a segmentation fault that occurs when attempting to access an unknown address in the kh_get_ucl_hash_caseless_node function. This can be triggered by a specially crafted input, potentially leading to a denial of service (DoS) or arbitrary code execution. The crash state indicates that the issue lies within the ucl_hash_search and ucl_include_file_single functions. The severity of the vulnerability is currently unknown.

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

At the moment, no specific workaround has been provided for this vulnerability. It is advised to monitor the official libucl repository for updates and apply the patch as soon as it becomes available.

Conclusion

In conclusion, a vulnerability has been identified in libucl that can result in a segmentation fault when accessing an unknown address. This vulnerability may have serious consequences, including denial of service or arbitrary code execution. It is crucial to stay informed about the progress of the fix and apply the patch as soon as it becomes available. For further assistance or support in addressing this vulnerability, 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 structures.

The vulnerability can potentially lead to a denial of service (DoS) or arbitrary code execution if exploited.

The maintainers of libucl are actively working on resolving the issue and a fix is expected to be released soon.

The specific versions affected by this vulnerability have not been disclosed. It is recommended to update to the latest version once a fix is available.

You can monitor the official libucl repository for updates and announcements regarding the resolution of this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for libucl.

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