How severe is CVE-2019-14867?

CVE-2019-14867 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-14867?

CVE-2019-14867 affects the following packages: ipa (PyPI), ipa (PyPI), ipa (PyPI), freeipa (PyPI), freeipa (PyPI), freeipa (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-14867?

Update ipa to 4.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14867 is resolved across your whole dependency graph.

How do I detect CVE-2019-14867 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ipa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-14867 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2019-14867 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-14867 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-14867?

CVE-2019-14867 has an EPSS (Exploit Prediction Scoring System) score of 7.4%, placing it in the 94th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-14867?

CVE-2019-14867 is classified as Code Injection (CWE-94), Uncontrolled Resource Consumption (CWE-400). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-14867 published, and has it been updated?

CVE-2019-14867 was published on November 27, 2019 and was last updated on October 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2019-14867 — ipa

HIGH

CVE-2019-14867 is a high-severity (CVSS 8.8) Code Injection vulnerability in ipa. A fix is available for ipa — see the affected versions and patch details below.

Code injection in FreeIPA

Also known asGHSA-7hpj-hfcr-5qwmPYSEC-2019-28PYSEC-2026-636

Published

Nov 27, 2019

Updated

Oct 29, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

7.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

🐍ipa🐍ipa🐍ipa🐍freeipa🐍freeipa🐍freeipa

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A 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.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ipa`	≥ 4.6.2&&< 4.6.7	4.6.7`pip install --upgrade 'ipa==4.6.7'`
🐍PyPI	`ipa`	≥ 4.7.0&&< 4.7.4	4.7.4`pip install --upgrade 'ipa==4.7.4'`
🐍PyPI	`ipa`	≥ 4.8.0&&< 4.8.3	4.8.3`pip install --upgrade 'ipa==4.8.3'`
🐍PyPI	`freeipa`	≥ 4.6.2&&< 4.6.7	4.6.7`pip install --upgrade 'freeipa==4.6.7'`
🐍PyPI	`freeipa`	≥ 4.7.0&&< 4.7.4	4.7.4`pip install --upgrade 'freeipa==4.7.4'`
🐍PyPI	`freeipa`	≥ 4.8.0&&< 4.8.3	4.8.3`pip install --upgrade 'freeipa==4.8.3'`

Affected Products

2 products · 5 configurations

fedorafedoraproject

2 versions

3031

Application

freeipafreeipa

≥ 4.8.0 && < 4.8.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ipa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ipa to 4.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14867 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw can be exploited by an unauthenticated attacker (PR:N) who could create a specially crafted "krbPrincipalKey" and send it to the IPA server (AV:N). The attack is relatively easy to conduct (AC:L), since all the attacker requires is a string which is long enough to write beyond the limits of the buffer on…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`ipa-0:4.6.5-11.el7_7.4`	RHSA-2020:0378
Red Hat Enterprise Linux 8	`idm:DL1-8010020191127093529.6573b795`	RHBA-2019:4268
Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions	`idm:DL1-8000020200217171713.2874843d`	RHSA-2020:1269

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-14867 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works