cve.bz

CVE-2023-22652 opensuse libeconf: Classic Buffer Overflow

6.5 mediumEPSS 0.6%

Medium (6.5) in opensuse libeconf. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
A Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in openSUSE libeconf leads to DoS via malformed config files. This issue affects libeconf: before 0.5.2.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-01-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-120 Buffer Copy without Checking Size of Input (Classic Buffer Overflow)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-22652 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-22652?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-22652?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-22652 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
openSUSE libeconffrom ? before 0.5.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11libeconf0.3.8-1+deb11u1DLA-4164-1
Debian12libeconf0.5.1+dfsg1-1+deb12u1DEBIAN-CVE-2023-22652
Debian13, 14libeconf0.5.2+dfsg1-1DEBIAN-CVE-2023-22652
Ubuntu22.04:LTSlibeconf0.3.8-1+deb11u1build0.22.04.1UBUNTU-CVE-2023-22652 USN-8368-1
Red Hatenterprise_linux:9::baseoslibeconf, libeconf-debuginfo, libeconf-debugsource and 1 more0:0.4.1-3.el9_2RHSA-2023:4347
SUSELinux Enterprise Micro 5.1, Linux Enterprise Micro 5.2, Manager Proxy 4.2 and 1 morelibeconf0.5.2-150300.3.11.1SUSE-SU-2023:3639-1
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4, Linux Enterprise Module for Basesystem 15 SP4 and 1 morelibeconf0.5.2-150400.3.6.1SUSE-SU-2023:3954-1
SUSELinux Enterprise Micro 5.5libeconf0.5.2-150400.3.6.1SUSE-SU-2023:3954-2 SUSE-SU-2024:2426-1
openSUSELeap 15.4, Leap 15.5libeconf0.5.2-150400.3.6.1SUSE-SU-2023:3954-1
AlmaLinux9libeconf0.4.1-3.el9_2ALSA-2023:4347
Rocky Linux9libeconf0:0.4.1-3.el9_2RLSA-2023:4347
Alpaquita23libeconf0.4.7-r1BELL-CVE-2023-22652

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 9libeconf-0:0.4.1-3.el9_2Fixed 2023-08-01RHSA-2023:4347

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-22652.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-120 (13).

References

Check your stackJSON