FedoraOperating system · Fedoraproject
CVE-2019-14867
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 · uneditedA flaw was found in IPA, all 4.6.x versions before 4.6.7, all 4.7.x versions before 4.7.4 and all 4.8.x versions before 4.8.3, in the way the internal function ber_scanf() was used in some components of the IPA server, which parsed kerberos key data. An unauthenticated attacker who could trigger parsing of the krb principal key could cause the IPA server to crash or in some conditions, cause arbitrary code to be executed on the server hosting the IPA server.
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 · high confidenceA use-after-free or buffer overflow vulnerability exists in the ber_scanf() function when parsing Kerberos principal key data in IPA server versions 4.6.x before 4.6.7, 4.7.x before 4.7.4, and 4.8.x before 4.8.3. The ber_scanf() function from the LDAP BER library is improperly used, allowing an unauthenticated attacker to trigger parsing of krb principal key data and cause server crash or potentially achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
FedoraOperating system
= 30= 31>= 4.6.0, < 4.6.7>= 4.7.0, < 4.7.4>= 4.8.0, < 4.8.3CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if FreeIPA server is installedOn Fedora or RHEL-based systems, run: rpm -qa | grep -i freeipa-serverAffected if No FreeIPA server packages are installed, the system is not affected
-
Identify the installed FreeIPA versionRun: rpm -q --queryformat '%{VERSION}' freeipa-serverAffected if The command returns a version lower than 4.6.7, 4.7.4, or 4.8.3 respectively for the 4.6.x, 4.7.x, or 4.8.x branches
-
Verify the full version string for precise comparisonRun: rpm -q --queryformat '%{VERSION}-%{RELEASE}' freeipa-serverAffected if The version falls within 4.6.0 to 4.6.6, 4.7.0 to 4.7.3, or 4.8.0 to 4.8.2
A system is affected if FreeIPA server version is 4.6.0 through 4.6.6, 4.7.0 through 4.7.3, or 4.8.0 through 4.8.2.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data4.6.74.7.44.8.3
Upgrade IPA server to version 4.6.7, 4.7.4, 4.8.3 or later. If immediate patching is not possible, restrict network access to IPA services and ensure Kerberos key parsing is not exposed to unauthenticated users.
Fix this in Fedora
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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