# CVE-2017-12133: Use after free in n/a

> Remote attackers can exploit a use-after-free flaw in glibc's UDP RPC client to potentially execute code or cause denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-12133, GHSA-v9xh-wvfv-7mhr, SUSE-SU-2018:0655-1, SUSE-SU-2018:0874-1, UBUNTU-CVE-2017-12133

## What is CVE-2017-12133?

CVE-2017-12133 is a medium-severity use after free vulnerability in Gnu Glibc, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free vulnerability in the clntudp_call function in sunrpc/clnt_udp.c in the GNU C Library (aka glibc or libc6) before 2.26 allows remote attackers to have unspecified impact via vectors related to error path.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glibc` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 2.11.3-17.110.9.2 |
| `glibc` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 2.11.3-17.110.9.2 |
| `glibc` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 2.11.3-17.110.9.2 |
| `glibc` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 2.22-62.10.1 |
| `glibc` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 2.22-62.10.1 |

Products: Gnu Glibc.

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

Upgrade to a fixed version.

## Is CVE-2017-12133 being exploited?

There is no known exploitation of CVE-2017-12133 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-12133 and fix it if it is affected.

What it is: CVE-2017-12133 is a medium-severity use after free vulnerability in Gnu Glibc, published on 7 Sep 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-12133 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-12133/ (Markdown: https://insights.sbomify.com/CVE-2017-12133/index.md)
```

## Sources

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

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