Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍 PyPI

GHSA-7hpj-hfcr-5qwm

HIGH

GHSA-7hpj-hfcr-5qwm is a high-severity (CVSS 8.8) Code Injection vulnerability in ipa. O3 Security confirms whether GHSA-7hpj-hfcr-5qwm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Code injection in FreeIPA

Also known asCVE-2019-14867PYSEC-2019-28PYSEC-2026-636
Published
Dec 6, 2021
Updated
Jul 6, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

Blast Radius

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
EcosystemPackageVulnerable rangeFix
🐍PyPIipa4.6.2&&< 4.6.74.6.7
🐍PyPIipa4.7.0&&< 4.7.44.7.4
🐍PyPIipa4.8.0&&< 4.8.34.8.3
🐍PyPIfreeipa4.6.2&&< 4.6.74.6.7
🐍PyPIfreeipa4.7.0&&< 4.7.44.7.4
🐍PyPIfreeipa4.8.0&&< 4.8.34.8.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ipa. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update ipa to 4.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7hpj-hfcr-5qwm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-7hpj-hfcr-5qwm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7hpj-hfcr-5qwm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-7hpj-hfcr-5qwm in your dependencies?

O3 detects GHSA-7hpj-hfcr-5qwm across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.