# CVE-2015-2698: Memory corruption in n/a

> Remote authenticated users can trigger memory corruption in MIT Kerberos, causing denial of service or potential code execution.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-2698, GHSA-v6gv-gg54-g3w6, MGASA-2015-0446, SUSE-SU-2015:2302-1, UBUNTU-CVE-2015-2698

## What is CVE-2015-2698?

CVE-2015-2698 is a high-severity memory corruption vulnerability in Mit Kerberos 5, published on 13 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The iakerb_gss_export_sec_context function in lib/gssapi/krb5/iakerb.c in MIT Kerberos 5 (aka krb5) 1.14 pre-release 2015-09-14 improperly accesses a certain pointer, which allows remote authenticated users to cause a denial of service (memory corruption) or possibly have unspecified other impact by interacting with an application that calls the gss_export_sec_context function.  NOTE: this vulnerability exists because of an incorrect fix for CVE-2015-2696.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-2698?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `krb5` | SUSE:Linux Enterprise Desktop 12 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Desktop 12 SP1 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Server 12 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Server 12 SP1 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 12 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 12 | All versions | 1.12.1-22.5 |
| `krb5` | SUSE:Linux Enterprise Software Development Kit 12 SP1 | All versions | 1.12.1-22.5 |

Products: Mit Kerberos 5.

## How do I fix CVE-2015-2698?

Apply the vendor's patch.

## Is CVE-2015-2698 being exploited?

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

## Other vulnerabilities in Mit Kerberos 5

- [CVE-2011-0285](https://insights.sbomify.com/CVE-2011-0285/): Use after free in n/a (critical 10.0)
- [CVE-2008-0947](https://insights.sbomify.com/CVE-2008-0947/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5902](https://insights.sbomify.com/CVE-2007-5902/): Integer overflow in n/a (critical 10.0)
- [CVE-2007-4743](https://insights.sbomify.com/CVE-2007-4743/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-3999](https://insights.sbomify.com/CVE-2007-3999/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2698 and fix it if it is affected.

What it is: CVE-2015-2698 is a high-severity memory corruption vulnerability in Mit Kerberos 5, published on 13 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2698 in the wild and no public exploit code.

Affected product: Mit Kerberos 5. 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-2015-2698/ (Markdown: https://insights.sbomify.com/CVE-2015-2698/index.md)
```

## Sources

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

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