Vulnerability in ipa-enrollment SLAPI plugin (CVE-2026-73199)
Summary
Vulnerability in ipa-enrollment SLAPI plugin (CVE-2026-73199). Risk of unauthorized operations or information disclosure. Exploitable via JOIN_OID.
Original description
The description as published by the source.
A flaw was found in the ipa-enrollment SLAPI plugin. A remote authenticated client can exploit a null pointer dereference vulnerability by sending a malformed Lightweight Directory Access Protocol (LDAP) extended operation. By omitting the request value for the JOIN_OID in the ipa-enrollment extended operation, an attacker can trigger a server crash, potentially causing a denial of service.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-73199 has been found in ipa-enrollment SLAPI plugin.
Attackers can target a specific entry point like JOIN_OID over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ipa-enrollment SLAPI plugin CVE-2026-73199" on the vendor's site.
CVE-2026-73199 (ipa-enrollment SLAPI plugin) — CWE-476 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: JOIN_OID
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-476) exists in ipa-enrollment SLAPI plugin. Attackers reach the vulnerable code path via JOIN_OID.
Check the vendor advisory for the affected versions of ipa-enrollment SLAPI plugin. Attack surface: JOIN_OID.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで ipa-enrollment SLAPI plugin を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web secalert@redhat.com
- web bugzilla.redhat.com
- web nvd.nist.gov
- web github.com