Alerts This Week
Warning Icon 1 758
Alerts This Week
Warning Icon 1 758

Gentoo: GLSA-202408-08 Normal: json-c Buffer Overflow Threat

gentoo
Calendar Grey August 7, 2024
Dist Gentoo Esm H88
The Gentoo GLSA-202408-09 addresses a critical security vulnerability in libxml2, along with detailed upgrade guidance.
A vulnerability has been discovered in json-c, which can lead to a stack buffer overflow.

Summary

Please review the CVE identifier referenced below for details.

Topics%20covered

Topics Covered

security advisory Gentoo buffer overflow upgrade instructions normal severity json-c

Resolution

All json-c users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/json-c-0.16"

References

[ 1 ] CVE-2021-32292 https://nvd.nist.gov/vuln/detail/CVE-2021-32292

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202408-08
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: json-c: Buffer Overflow
Date: August 07, 2024
Bugs: #918555
ID: 202408-08

Topics%20covered

Topics Covered

security advisory Gentoo buffer overflow upgrade instructions normal severity json-c

Synopsis

A vulnerability has been discovered in json-c, which can lead to a stack buffer overflow.

Background

json-c is a JSON implementation in C.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected --------------- ------------ ------------ dev-libs/json-c < 0.16 >= 0.16

Impact

A stack-buffer-overflow exists in the auxiliary sample program json_parse which is located in the function parseit.

Workaround

There is no known workaround at this time.

Your message here