# CVE-2017-15671: Denial of service in n/a

> A memory leak in glibc's glob function when processing long usernames with GLOB_TILDE can lead to denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-15671, GHSA-3gv3-62jc-35qm, SUSE-SU-2018:4067-1, UBUNTU-CVE-2017-15671

## What is CVE-2017-15671?

CVE-2017-15671 is a medium-severity denial of service vulnerability in Gnu Glibc, published on 20 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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).

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

## Which versions are affected by CVE-2017-15671?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glibc` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 2.11.3-17.110.24.2 |
| `glibc` | SUSE:Linux Enterprise Server 11 SP3-LTSS | All versions | 2.11.3-17.110.24.2 |
| `glibc` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 2.11.3-17.110.24.2 |
| `glibc` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 2.11.3-17.110.24.2 |
| `glibc` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 2.11.3-17.110.24.2 |
| `glibc` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.11.3-17.110.24.2 |

Products: Gnu Glibc.

## How do I fix CVE-2017-15671?

Upgrade to a fixed version.

## Is CVE-2017-15671 being exploited?

There is no known exploitation of CVE-2017-15671 in the wild and no public exploit code.

## Other vulnerabilities in Gnu Glibc

- [CVE-2026-5450](https://insights.sbomify.com/CVE-2026-5450/): scanf %mc off-by-one heap buffer overflow (critical 9.8)
- [CVE-2023-25139](https://insights.sbomify.com/CVE-2023-25139/): Memory corruption in n/a (critical 9.8)
- [CVE-1999-0199](https://insights.sbomify.com/CVE-1999-0199/): Other in n/a (critical 9.8)
- [CVE-2019-1010022](https://insights.sbomify.com/CVE-2019-1010022/): Security feature bypass in glibc (critical 9.8)
- [CVE-2005-3590](https://insights.sbomify.com/CVE-2005-3590/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15671 and fix it if it is affected.

What it is: CVE-2017-15671 is a medium-severity denial of service vulnerability in Gnu Glibc, published on 20 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-15671 in the wild and no public exploit code.

Affected product: Gnu Glibc. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-15671/ (Markdown: https://insights.sbomify.com/CVE-2017-15671/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-15671
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-15671
- OSV: https://osv.dev/vulnerability/CVE-2017-15671

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-15671/
Summaries are generated and may contain mistakes; the official description above is the record.