Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-2697

krb5: build_principal() memory flaw

Overview

Published
9 Nov 2015
Modified
6 May 2026
Medium CVE
0 Registry packages
18 OS packages
5 Linux distributions
Yes Fix available

Description

The build_principal_va function in lib/krb5/krb/bld_princ.c in MIT Kerberos 5 (aka krb5) before 1.14 allows remote authenticated users to cause a denial of service (out-of-bounds read and KDC crash) via an initial '\0' character in a long realm field within a TGS request.

Source: OX vulnerability database

Severity

4 · MEDIUM

CVSS 2.0 base score, scored by NVD.

Access vector
Network
Access complexity
Low
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:S/C:N/I:N/A:P

Weakness: CWE-125

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
krb5
Red Hat fixes for CVE-2015-2697
ReleasePackageFixed in
7 krb5 +7 wont fix

debian 4 releases · 1 package

fixed 4
krb5
debian fixes for CVE-2015-2697
ReleasePackageFixed in
11 krb5 1.13.2+dfsg-3
12 krb5 1.13.2+dfsg-3
13 krb5 1.13.2+dfsg-3
14 krb5 1.13.2+dfsg-3

echo 1 release · 1 package

fixed 1
krb5
echo fixes for CVE-2015-2697
ReleasePackageFixed in
krb5 1.13.2+dfsg-3

openSUSE 1 release · 1 package

fixed 1
krb5
openSUSE fixes for CVE-2015-2697
ReleasePackageFixed inAdvisory
Tumbleweed krb5 +11 1.15-1.1 openSUSE-SU-2024:10004-1

root.io debian 2 releases · 1 package

fixed 2
rootio-krb5
root.io debian fixes for CVE-2015-2697
ReleasePackageFixed in
12 rootio-krb5 1.13.2+dfsg-3
13 rootio-krb5 1.13.2+dfsg-3

References

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.