Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2017-15671

glibc: Memory leak in glob with GLOB_TILDE

Overview

Published
20 Oct 2017
Modified
17 Jun 2026
Medium CVE
0 Registry packages
11 OS packages
5 Linux distributions
Yes Fix available

Description

The glob function in glob.c in the GNU C Library (aka glibc or libc6) before 2.27, when invoked with GLOB_TILDE, could skip freeing allocated memory when processing the ~ operator with a long user name, potentially leading to a denial of service (memory leak).

Source: OX vulnerability database

Severity

5.9 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-772

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

Red Hat 1 release · 1 package

wont fix 1
compat-glibc
Red Hat fixes for CVE-2017-15671
ReleasePackageFixed in
7 compat-glibc +8 wont fix

debian 5 releases · 1 package

fixed 5
glibc
debian fixes for CVE-2017-15671
ReleasePackageFixed in
11 glibc 2.25-3
12 glibc 2.25-3
13 glibc 2.25-3
14 glibc 2.25-3
9 glibc 2.24-11+deb9u4

echo 1 release · 1 package

fixed 1
glibc
echo fixes for CVE-2017-15671
ReleasePackageFixed in
glibc 2.25-3

root.io debian 3 releases · 1 package

fixed 3
rootio-glibc
root.io debian fixes for CVE-2017-15671
ReleasePackageFixed in
11 rootio-glibc 2.25-3
12 rootio-glibc 2.25-3
13 rootio-glibc 2.25-3

seal Red Hat 1 release · 1 package

fixed 1
glibc
seal Red Hat fixes for CVE-2017-15671
ReleasePackageFixed in
7 glibc +1 2.17-326.el7_9.3+sp999

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.