Security Advisory

CVE-2023-6780: glibc syslog() Integer Overflow

Last updated:
  • CVE-2023-6780

CVE-2023-6780 is an integer overflow in glibc's __vsyslog_internal(), the code behind syslog() and vsyslog(): a very long log message makes the buffer size calculation wrap. Red Hat says the only known impact is a failed allocation that drops the message. It affects glibc 2.37, 2.38 and the 2.36 branch from 2.36-16, and is fixed in 2.39, 2.38-44, 2.37-59 and 2.36-128. NVD scores it 5.3.

Vulnerability summary

CVSS base score

5.3

Medium severity

EPSS score (FIRST)

2.7%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

No

Not listed

Published

Vulnerability ID: CVE-2023-6780 · Source: NVD

Affected components

ComponentCPEVersion range
GNU C Library (glibc) syslog()/vsyslog()cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*2.37 to before 2.39 (NVD); per GLIBC-SA-2024-0003 also the 2.36 branch from 2.36-16; fixed in 2.39, 2.38-44, 2.37-59, 2.36-128
Debian glibc packagepkg:deb/debian/glibcbookworm 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 carries 2.38-44, 2023.11.1 carries 2.38-27; 2023.02.10 carries 2.36-128 (fixed), 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-6780 is an integer overflow in __vsyslog_internal(), the glibc function behind syslog() and vsyslog(). The CVE record says it "occurs when these functions are called with a very long message, leading to an incorrect calculation of the buffer size to store the message, resulting in undefined behavior." NVD gives a Primary score of 5.3, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, and lists CWE-131 (incorrect calculation of buffer size) and CWE-190 (integer overflow). Red Hat, the CNA, gives the same 5.3 vector with CWE-131 and rates it Low. NVD published it on 2024-01-31 (NVD, CVE record).

What is the real impact of CVE-2023-6780?

The glibc advisory GLIBC-SA-2024-0003 states the bug in one line: __vsyslog_internal "calculated a buffer size by adding two integers, but did not first check if the addition would overflow." Red Hat's assessment is narrower than the CVSS vector suggests: the issue "can only result in a memory allocation failure when the syslog function is called with a very long message, preventing the output of the message", and that is the only known impact (Red Hat). An attacker therefore needs a way to make a program on the device log an extremely long string, and the result is a lost log line, not code execution. Qualys found this bug and the off-by-one CVE-2023-6779 on 2023-12-07 while reviewing the patch for CVE-2023-6246, the heap overflow in the same function, and its syslog advisory of 2024-01-30 calls both "minor vulnerabilities".

Which glibc versions and devices are affected?

GLIBC-SA-2024-0003 names the vulnerable commit in glibc 2.37 and again at 2.36-16 on the 2.36 release branch, where the syslog rework was backported. Fixes are in glibc 2.39 and in branch commits 2.38-44, 2.37-59 and 2.36-128; these numbers are one higher than the fixes for CVE-2023-6779, so a build that only reached 2.36-127 or 2.38-43 still carries this bug. NVD's CPE range is 2.37 up to (excluding) 2.39 and does not cover the 2.36 branch builds.

  • 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 lists RHEL 6 to 9 as not affected, because no Red Hat product uses glibc 2.37.
  • Buildroot bumped glibc to 2.38-44-gd37c2b20…, the exact 2.38 fix commit, on 2024-02-01; the commit message names CVE-2023-6246, CVE-2023-6779 and CVE-2023-6780 (Buildroot commit 75e7c7ba). Buildroot 2023.11.2 carries 2.38-44, while 2023.11.1 carries 2.38-27. On the 2023.02 LTS line, 2023.02.10 carries 2.36-128-gb9b7d6a2…, which is the 2.36 fix commit, and 2023.02.9 carries 2.36-118 (Buildroot 2023.02.10 glibc.mk).

Siemens ProductCERT SSA-082556 lists CVE-2023-6780 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, scored 5.3. As of 2026-11-19 those rows read "Currently no fix is available"; Siemens states that 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-6780.

How do you fix CVE-2023-6780?

Move to glibc 2.39 or later, or to a branch build at or after the fix commit for your line: 2.38-44, 2.37-59 or 2.36-128. On Debian bookworm that means 2.36-9+deb12u4 or later; on Buildroot it means 2023.11.2, 2024.02 or later, or 2023.02.10 on the LTS line. The same patch set closes CVE-2023-6246 and CVE-2023-6779, so treat the three as one update, and rebuild static binaries because they carry their own copy of syslog(). If an update has to wait, cap the length of strings that reach syslog() from network input in your own daemons. Our glibc, uClibc and musl vulnerabilities guide shows how to find the C library and its branch version in a firmware image; images from the same period usually also need the fix for CVE-2023-4911, the loader tunables overflow.

Is CVE-2023-6780 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 2024-01-31, records exploitation as "poc", automatable as "no" and technical impact as "partial". FIRST EPSS gives it 0.027, the 86.3rd percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS).

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • NVD: integer overflow in __vsyslog_internal, called by syslog and vsyslog, with a very long message, incorrect buffer size calculation, undefined behavior; affects glibc 2.37 and newer. NVD Primary CVSS v3.1 5.3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L; NVD CWE-131 and CWE-190; Red Hat secondary 5.3 same vector, CWE-131; CPE glibc 2.37 to before 2.39, Fedora 38 and 39; status Modified; published 2024-01-31. — NVD
  • CVE.org: state PUBLISHED, CNA Red Hat, published 2024-01-31; CVSS 3.1 5.3, CWE-131, Red Hat severity Low; 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 (2024-01-31) exploitation poc, automatable no, technical impact partial; Siemens ADP reference SSA-082556. — CVE.org
  • GLIBC-SA-2024-0003 (CVE-2023-6780, public 2024-01-30): __vsyslog_internal calculated a buffer size by adding two integers without checking for overflow. Vulnerable commit 52a5be0 (2.37) and b0e7888 (2.36-16); fix commits ddf542d (2.39), d37c2b2 (2.38-44), 2b58cba (2.37-59), b9b7d6a (2.36-128). — glibc
  • Red Hat: the issue can only result in a memory allocation failure when syslog is called with a very long message, preventing output of the message; this is the only known impact. glibc as shipped with Red Hat products is not affected because the issue was introduced in 2.37; RHEL 6, 7, 8, 9 not affected; Bugzilla 2254396; threat severity Low. — Red Hat
  • Qualys syslog advisory (2024-01-30): while reviewing the CVE-2023-6246 patch on 2023-12-07 Qualys found two more minor vulnerabilities in __vsyslog_internal (an off-by-one buffer overflow and an integer overflow); coordinated release 2024-01-30. — Qualys
  • 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 ddf542da and GLIBC-SA-2024-0003 referenced. — Debian security tracker
  • Buildroot commit 75e7c7ba (committed 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; glibc.mk GLIBC_VERSION: 2023.11.1 2.38-27, 2023.11.2 2.38-44-gd37c2b20, 2023.02.9 2.36-118, 2023.02.10 2.36-128-gb9b7d6a2. — Buildroot
  • Siemens SSA-082556 (V1.7, last update 2026-10-13): CVE-2023-6780 (CVSS v3.1 5.3, CWE-131) 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, all versions >= V3.1.5, in rows marked 'Currently no fix is available'; V3.1.5 no longer maintained, update to the latest version. SSA-019113 (V3.1.6) does not list CVE-2023-6780. — Siemens ProductCERT
  • Not in CISA KEV catalog version 2026.11.18 (1,786 entries); EPSS 0.02711, percentile 0.86279, dataset 2026-11-18. — CISA KEV / FIRST EPSS

Related advisories

Sources

  1. NVD
  2. glibc advisory GLIBC-SA-2024-0003 (CVE-2023-6780), glibc source mirror
  3. Red Hat CVE page: CVE-2023-6780
  4. Qualys Security Advisory: CVE-2023-6246, heap-based buffer overflow in glibc's syslog()
  5. Debian security tracker: CVE-2023-6780
  6. Buildroot commit 75e7c7ba: glibc security bump to 2.38-44
  7. Buildroot 2023.02.10 package/glibc/glibc.mk
  8. Siemens ProductCERT SSA-082556
  9. Siemens ProductCERT SSA-019113
  10. CVE.org record CVE-2023-6780 (CNA: Red Hat)
  11. CISA KEV
  12. FIRST EPSS

Frequently asked questions

Can CVE-2023-6780 be used to run code on a device?

No such impact is known. Red Hat states that the issue can only cause a memory allocation failure when syslog() is called with a very long message, which prevents that message from being logged, and that this is the only known impact. NVD's 5.3 vector rates it as low availability impact with no confidentiality or integrity impact (per Red Hat and NVD).

Which glibc versions fix CVE-2023-6780?

glibc 2.39 and the branch commits 2.38-44, 2.37-59 and 2.36-128. These are one commit later than the CVE-2023-6779 fixes, so a 2.36-127 or 2.38-43 build fixes CVE-2023-6779 but still carries CVE-2023-6780 (per GLIBC-SA-2024-0002 and GLIBC-SA-2024-0003).

Which embedded builds and industrial products ship a fix or list CVE-2023-6780?

Buildroot fixed it on 2024-02-01 by moving to glibc 2.38-44, shipped in 2023.11.2, and its 2023.02.10 LTS release carries the 2.36-128 fix commit. 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-6780 exploited in the wild?

It is not in the CISA KEV catalog as of 2026-11-19 (catalog version 2026.11.18). CISA's SSVC entry records exploitation as poc and automatable as no. FIRST EPSS gives it 0.027, the 86.3rd percentile, in the 2026-11-18 dataset (per CISA KEV, CVE.org and FIRST EPSS).