CVE-2023-6779 is an off-by-one heap buffer overflow in glibc's __vsyslog_internal(), the code behind syslog() and vsyslog(), triggered when a program logs a message longer than INT_MAX bytes and leading to a crash. It came in with glibc 2.37 and the 2.36 branch from 2.36-16, and is fixed in 2.39 and branch builds 2.38-43, 2.37-58 and 2.36-127. NVD scores it 7.5.
Vulnerability summary
CVSS base score
7.5
High severity
EPSS score (FIRST)
3.2%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2023-6779 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| GNU C Library (glibc) syslog()/vsyslog() | cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:* | 2.37 to before 2.39 (NVD); per GLIBC-SA-2024-0002 also the 2.36 branch from 2.36-16; fixed in 2.39, 2.38-43, 2.37-58, 2.36-127 |
| Debian glibc package | pkg:deb/debian/glibc | bookworm fixed in 2.36-9+deb12u4 (DSA-5611-1); unstable fixed in 2.37-15; buster and bullseye not affected (Debian security tracker) |
| Buildroot package/glibc | — | Bumped to glibc-2.38-44-gd37c2b20 on 2024-02-01 (commit 75e7c7ba); 2023.11.2 and 2024.02 carry 2.38-44, 2023.11 and 2023.11.1 carry 2.38-27; 2023.02.10 carries 2.36-128, 2023.02.9 carries 2.36-118 |
| Siemens SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP and SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (GNU/Linux subsystem) | — | Firmware V3.1.5; row reads 'Currently no fix is available' as of 2026-11-19, V3.1.5 no longer maintained, Siemens recommends the latest version (Siemens SSA-082556); not listed in SSA-019113 for V3.1.6 |
What does this mean for affected devices?
CVE-2023-6779 is an off-by-one heap buffer overflow in __vsyslog_internal(), the glibc function behind syslog() and vsyslog(). NVD classes it CWE-787 (out-of-bounds write) and gives a Primary score of 7.5, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Red Hat, the CNA, scores it 8.2, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H, with CWE-122 (heap-based buffer overflow), and its own CVE page names CWE-193 (off-by-one error). The CVE record says the bug "occurs when these functions are called with a message bigger than INT_MAX bytes, leading to an incorrect calculation of the buffer size to store the message, resulting in an application crash." NVD published it on 2024-01-31 (NVD, CVE record).
What goes wrong in the code?
The glibc advisory GLIBC-SA-2024-0002 explains that __vsyslog_internal "used the return value of snprintf/vsnprintf to calculate buffer sizes for memory allocation. If these functions (for any reason) failed and returned -1, the resulting buffer would be too small to hold output." Qualys found it, together with the integer overflow CVE-2023-6780 (GLIBC-SA-2024-0003), on 2023-12-07 while reviewing the patch for CVE-2023-6246, the larger syslog() heap overflow in the same function. The Qualys advisory, also posted to oss-security on 2024-01-30, calls the two "minor vulnerabilities". To reach this one, a program has to pass a single log message longer than INT_MAX bytes to syslog() or vsyslog(); the impact the CVE record describes is a crash of that program.
Which glibc versions and devices are affected?
GLIBC-SA-2024-0002 lists the vulnerable commit as glibc 2.37, and also as 2.36-16 on the 2.36 release branch, where it arrived as part of a backported syslog fix. Fixes are in glibc 2.39 and in branch commits 2.38-43, 2.37-58 and 2.36-127. NVD's CPE range is 2.37 up to (excluding) 2.39, so it does not cover the 2.36 branch builds that GLIBC-SA-2024-0002 names; match on branch commit counts, not on the release number alone.
- Debian fixed bookworm (glibc 2.36) in 2.36-9+deb12u4 with DSA-5611-1 and lists buster and bullseye as not affected because the vulnerable code is absent (Debian security tracker).
- Red Hat states that the glibc shipped in its products is not affected, because the issue was introduced in 2.37 and no Red Hat product uses that version (Red Hat).
- Buildroot bumped glibc to
glibc-2.38-44-gd37c2b20…on 2024-02-01 with the commit message naming CVE-2023-6246, CVE-2023-6779 and CVE-2023-6780 (Buildroot commit 75e7c7ba). Releases 2023.11.2 and 2024.02 carry that version; 2023.11 and 2023.11.1 carry 2.38-27. The 2023.02 LTS line carries 2.36-118 in 2023.02.9 and 2.36-128 in 2023.02.10 (Buildroot 2023.02.10glibc.mk), so by the branch commit counts in GLIBC-SA-2024-0002, 2023.02.9 and earlier 2023.02.x images built on the 2.36 branch after 2.36-16 need checking.
Siemens ProductCERT SSA-082556 lists CVE-2023-6779 for the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518-4 PN/DP MFP and 1518F-4 PN/DP MFP, including the SIPLUS S7-1500 CPU 1518-4 PN/DP MFP, firmware V3.1.5, and scores it 8.2. As of 2026-11-19 that row reads "Currently no fix is available", and Siemens says V3.1.5 is no longer maintained and recommends updating to the latest version; SSA-019113, which covers V3.1.6, does not list CVE-2023-6779.
How do you fix CVE-2023-6779?
Move to glibc 2.39 or later, or to a branch build that contains the Fix-Commit for your line: 2.38-43, 2.37-58 or 2.36-127 or later. On Debian bookworm that means 2.36-9+deb12u4 or later. The same patch set closes CVE-2023-6246 and CVE-2023-6780, so treat the three as one update. Static binaries carry their own copy of syslog() and have to be rebuilt. Our glibc, uClibc and musl vulnerabilities guide shows how to identify the C library and its exact branch version in a firmware image. Images in that range usually also need the fix for CVE-2023-4911, the loader tunables overflow, and older images still turn up CVE-2015-7547 in the resolver.
Is CVE-2023-6779 exploited?
It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18, 1,786 entries). CISA's SSVC entry, dated 2025-06-13, records exploitation as "none", automatable as "no" and technical impact as "partial". Qualys sent a proof of concept to Red Hat during disclosure; the proof of concept and exploit in its published advisory cover CVE-2023-6246. FIRST EPSS gives it 0.032, the 88.2nd percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).
Evidence
- NVD: off-by-one heap-based buffer overflow in __vsyslog_internal, called by syslog and vsyslog, with a message bigger than INT_MAX bytes, leading to an application crash; affects glibc 2.37 and newer. NVD Primary CVSS v3.1 7.5 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, CWE-787; Red Hat secondary 8.2 C:N/I:L/A:H, CWE-122; CPE glibc 2.37 to before 2.39, Fedora 38 and 39; published 2024-01-31T14:15:48.700. — NVD
- CVE.org: CNA Red Hat, published 2024-01-31; CVSS 3.1 8.2, CWE-122, Red Hat severity Important; glibc 2.39 unaffected; RHEL 6 to 9 unaffected; reported to Red Hat 2023-12-08, public 2024-01-30; credit Qualys Threat Research Unit; CISA ADP SSVC (2025-06-13) exploitation none, automatable no, technical impact partial; Siemens ADP reference SSA-082556. — CVE.org
- GLIBC-SA-2024-0002 (CVE-2023-6779, public 2024-01-30): __vsyslog_internal used snprintf/vsnprintf return values for buffer sizes; a -1 return made the buffer too small. Vulnerable commit 52a5be0 (2.37) and b0e7888 (2.36-16); fix commits 7e5a0c2 (2.39), d033831 (2.38-43), 67062ec (2.37-58), 2bc9d7c (2.36-127). GLIBC-SA-2024-0003 is CVE-2023-6780 (integer overflow). — glibc
- Qualys syslog advisory (2024-01-30): while reviewing the CVE-2023-6246 patch on 2023-12-07 Qualys found two more minor vulnerabilities in the same function (off-by-one buffer overflow and integer overflow) and sent analysis, proof of concept and patch proposal to Red Hat; Red Hat assigned CVE-2023-6779 to the off-by-one on 2023-12-13; coordinated release 2024-01-30. — Qualys / oss-security
- Debian: bookworm fixed 2.36-9+deb12u4 (DSA-5611-1), unstable 2.37-15; buster and bullseye not affected (vulnerable code not present); fix commit 7e5a0c28 and GLIBC-SA-2024-0002 referenced. — Debian security tracker
- Red Hat: glibc as shipped with Red Hat products is not affected because the issue was introduced in glibc 2.37, which no Red Hat product uses; CWE-193 off-by-one error; Bugzilla 2254395. — Red Hat
- Buildroot commit 75e7c7ba (2024-02-01) 'package/{glibc, localedef}: security bump to version glibc-2.38-44-gd37c2b20...' fixes CVE-2023-6246, CVE-2023-6779 and CVE-2023-6780. Buildroot's glibc.mk sets GLIBC_VERSION to 2.38-27 in releases 2023.11 and 2023.11.1, to 2.38-44 in 2023.11.2 and 2024.02, to 2.36-118 in 2023.02.9 and to 2.36-128 in 2023.02.10. — Buildroot
- Siemens SSA-082556 (V1.7, last update 2026-10-13): CVE-2023-6779 listed for the GNU/Linux subsystem of SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, 1518F-4 PN/DP MFP and SIPLUS S7-1500 CPU 1518-4 PN/DP MFP, firmware V3.1.5, in rows marked 'Currently no fix is available'; V3.1.5 no longer maintained, update to the latest version; CVSS v3.1 8.2; SSA-019113 (V3.1.6) does not list CVE-2023-6779. — Siemens ProductCERT
- Not in CISA KEV catalog version 2026.11.18 (1,786 entries); EPSS 0.03153, percentile 0.88211, dataset 2026-11-18. — CISA KEV / FIRST EPSS

Related advisories
Sources
- NVD
- glibc advisory GLIBC-SA-2024-0002 (CVE-2023-6779), glibc source mirror
- glibc advisory GLIBC-SA-2024-0003 (CVE-2023-6780), glibc source mirror
- Qualys Security Advisory: CVE-2023-6246, heap-based buffer overflow in glibc's syslog()
- oss-security: Qualys syslog advisory post (2024-01-30)
- Debian security tracker: CVE-2023-6779
- Red Hat CVE page: CVE-2023-6779
- Buildroot commit 75e7c7ba: glibc security bump to 2.38-44
- Buildroot 2023.02.10 package/glibc/glibc.mk
- Siemens ProductCERT SSA-082556
- Siemens ProductCERT SSA-019113
- CVE.org record CVE-2023-6779 (CNA: Red Hat)
- CISA KEV
- FIRST EPSS
Frequently asked questions
Which glibc versions does CVE-2023-6779 affect?
glibc 2.37 and 2.38, and the 2.36 release branch from commit 2.36-16, where the vulnerable change was backported. It is fixed in 2.39 and in branch commits 2.38-43, 2.37-58 and 2.36-127. NVD's CPE range covers only 2.37 to before 2.39 (per GLIBC-SA-2024-0002 and NVD).
What does an attacker need to trigger CVE-2023-6779?
A program on the device has to call syslog() or vsyslog() with a message bigger than INT_MAX bytes; the size calculation then goes wrong and the program crashes. Qualys found it while reviewing the CVE-2023-6246 patch and called it a minor vulnerability (per the CVE.org record, GLIBC-SA-2024-0002 and the Qualys syslog advisory).
How is CVE-2023-6779 different from CVE-2023-6246 and CVE-2023-6780?
All three are in __vsyslog_internal() and were disclosed together on 2024-01-30. CVE-2023-6246 is the heap overflow Qualys exploited for root on Fedora 38, CVE-2023-6779 is the off-by-one overflow when snprintf/vsnprintf fail, and CVE-2023-6780 is an integer overflow in the buffer size addition; the same glibc updates fix all three (per the Qualys syslog advisory and GLIBC-SA-2024-0001 to 0003).
Which embedded builds and industrial products ship a fix or list CVE-2023-6779?
Buildroot fixed it on 2024-02-01 by moving to glibc 2.38-44, shipped in 2023.11.2 and 2024.02, and its 2023.02.10 release carries 2.36-128. Debian bookworm is fixed in 2.36-9+deb12u4. Siemens lists it for the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP GNU/Linux subsystem at firmware V3.1.5, with no fix for that version as of 2026-11-19 (per the Buildroot repository, the Debian security tracker and Siemens SSA-082556).
Is CVE-2023-6779 exploited in the wild?
It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18), and CISA's SSVC entry records exploitation as none and automatable as no. FIRST EPSS gives it 0.032, the 88.2nd percentile, in the 2026-11-18 dataset (per CISA KEV, CVE.org and FIRST EPSS).
Questions about this page?