CVE-2017-15671
glibc: Memory leak in glob with GLOB_TILDE
Overview
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
| Release | Package | Fixed in |
|---|---|---|
| 7 | compat-glibc +8 | wont fix |
debian 5 releases · 1 package
fixed 5
glibc
| Release | Package | Fixed 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
| Release | Package | Fixed in |
|---|---|---|
| glibc | 2.25-3 |
root.io debian 3 releases · 1 package
fixed 3
rootio-glibc
| Release | Package | Fixed 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
| Release | Package | Fixed in |
|---|---|---|
| 7 | glibc +1 | 2.17-326.el7_9.3+sp999 |
References
- www.securityfocus.com http://www.securityfocus.com/bid/101517
- access.redhat.com https://access.redhat.com/security/cve/CVE-2017-15671
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2017-15671
- sourceware.org https://sourceware.org/bugzilla/show_bug.cgi?id=22325
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2017-15671
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.