How severe is CVE-2019-10195?

CVE-2019-10195 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-10195?

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

How do I fix CVE-2019-10195?

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

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

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

No public exploit code has been indexed for CVE-2019-10195 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-10195?

CVE-2019-10195 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th 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-10195?

CVE-2019-10195 is classified as Information Exposure (CWE-200), CWE-532 (CWE-532). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2019-10195 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

MEDIUM severity

CVE-2019-10195 — freeipa

MEDIUM

CVE-2019-10195 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in freeipa. A fix is available for freeipa — see the affected versions and patch details below.

FreeIPA logs passwords embedded in commands in calls using batch

Also known asGHSA-w4q7-f34x-vpgcPYSEC-2019-168PYSEC-2019-22

Published

Nov 27, 2019

Updated

Oct 29, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% 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

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

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 that FreeIPA's batch processing API logged operations. This included passing user passwords in clear text on FreeIPA masters. Batch processing of commands with passwords as arguments or options is not performed by default in FreeIPA but is possible by third-party components. An attacker having access to system logs on FreeIPA masters could use this flaw to produce log file content with passwords exposed.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`freeipa`	≥ 4.6.0&&< 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'`
🐍PyPI	`ipa`	≥ 4.6.0&&< 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'`

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 freeipa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update freeipa to 4.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10195 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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 HatModerate

This vulnerability exists in the server component of FreeIPA. Client packages are not affected.

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-10195 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works