dbcve.org
Kerberos 5Application · Mit

CVE-2014-5352

HIGH · 9.0 CVSS v2.0 Published 2015-02-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The krb5_gss_process_context_token function in lib/gssapi/krb5/process_context_token.c in the libgssapi_krb5 library in MIT Kerberos 5 (aka krb5) through 1.11.5, 1.12.x through 1.12.2, and 1.13.x before 1.13.1 does not properly maintain security-context handles, which allows remote authenticated users to cause a denial of service (use-after-free and double free, and daemon crash) or possibly execute arbitrary code via crafted GSSAPI traffic, as demonstrated by traffic to kadmind.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Kerberos 5Application
Affected:= 1.11= 1.11.1= 1.11.2= 1.11.3= 1.11.4= 1.11.5= 1.12= 1.12.1= 1.12.2= 1.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix High confidence

krb5-1.11.6 or later for 1.11.x; krb5-1.12.3 or later for 1.12.x; krb5-1.13.1 or later for 1.13.x

  1. 1. Identify the current installed version of MIT Kerberos 5 (krb5) using: rpm -q krb5-libs or dpkg -l | grep krb5
  2. 2. Based on your current version, upgrade to the fixed release: for 1.11.x upgrade to 1.11.6 or later; for 1.12.x upgrade to 1.12.3 or later; for 1.13.x upgrade to 1.13.1 or later
  3. 3. On RHEL/CentOS/Fedora: run 'yum update krb5-libs krb5-server krb5-workstation'
  4. 4. On Debian/Ubuntu: run 'apt-get update && apt-get install krb5-kdc krb5-admin-server krb5-user'
  5. 5. On SUSE/openSUSE: run 'zypper update krb5-server krb5-client'
  6. 6. Restart any Kerberos-related services (kadmind, krb5kdc) to load the updated libraries
  7. 7. Verify the fix is applied by checking the version: krb5-config --version
Caveat Minor - upgrading within same minor version should be low risk; verify custom GSSAPI application compatibility before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-5352 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-5352 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data