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

> A double free vulnerability in MIT Kerberos 5 allows attackers to potentially execute code or cause denial of service via error handling paths.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 13 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-11462, GHSA-rr2f-jhmq-594w, SUSE-SU-2017:2659-1, UBUNTU-CVE-2017-11462

## What is CVE-2017-11462?

CVE-2017-11462 is a critical use after free vulnerability in Fedoraproject Fedora, published on 13 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double free vulnerability in MIT Kerberos 5 (aka krb5) allows attackers to have unspecified impact via vectors involving automatic deletion of security contexts on error.

Weakness: CWE-415 (Double Free)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krb5` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.12.5-40.13.1 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 1.12.5-40.13.1 |

Products: Fedoraproject Fedora, Mit Kerberos 5.

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

Apply the vendor's patch.

## Is CVE-2017-11462 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11462 is a critical use after free vulnerability in Fedoraproject Fedora, published on 13 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-11462 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-11462/ (Markdown: https://insights.sbomify.com/CVE-2017-11462/index.md)
```

## Sources

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

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