CVE-2012-1012 json
server/server_stubs.c in the kadmin protocol implementation in MIT Kerberos 5 (aka krb5) 1.10 before 1.10.1 does not properly restrict acce…
published 2012-06-07 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-1050
- cvss
- 5.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
server/server_stubs.c in the kadmin protocol implementation in MIT Kerberos 5 (aka krb5) 1.10 before 1.10.1 does not properly restrict access to (1) SET_STRING and (2) GET_STRINGS operations, which might allow remote authenticated administrators to modify or read string attributes by leveraging the global list privilege.
Patch / fix
- krb5 Debian 14, Debian 13, Debian 12 1.10.1+dfsg-1
debian advisories DEBIAN-CVE-2012-1012
- krb5 openSUSE Tumbleweed 1.15-1.1
opensuse advisories openSUSE-SU-2024:10004-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-1012 updated cvss 3.6
krb5: flaw in access control handling for strings in kadmin
-
Red Hat Enterprise Linux 5 krb5 Red Hat Enterprise Linux 6 krb5, libkadm5, krb5-libs, krb5-server, krb5-server-ldap, krb5-workstation, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
Sources
- CVE List CVE-2012-1012
- NVD CVE-2012-1012
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.