Vulnerability in Dogtag PKI (CVE-2020-15720)

Summary

Vulnerability in Dogtag PKI (CVE-2020-15720). Confidential information can be exposed externally. Mitigation: upgrade to 10.9.0-b1 or later.

Original description

The description as published by the source.

In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests certificate validation. Since the verify parameter was hard-coded in all request functions, it was not possible to override the setting. As a result, tools making use of this class, such as the pki-server command, may have been vulnerable to Person-in-the-Middle attacks in certain non-localhost use cases. This is fixed in 10.9.0-b1.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

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-2020-15720 has been found in Dogtag PKI.
Confidential information can be exposed externally.
What to do: upgrade Dogtag PKI to 10.9.0-b1 or later.
If unsure, ask your IT team or search "Dogtag PKI CVE-2020-15720" on the vendor's site.

CVE-2020-15720 (Dogtag PKI)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 10.9.0-b1 — apply immediately
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.

❓ What is the problem

A vulnerability (unclassified) exists in Dogtag PKI.

📍 Affected scope

Check the vendor advisory for the affected versions of Dogtag PKI.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 10.9.0-b1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Dogtag PKI を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade Dogtag PKI to 10.9.0-b1
```
ステージング環境で 10.9.0-b1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2020-15720 dogtag-pki Fixed in: 10.9.1-1