NVD / CVE Program· CNA mitre

CVE-2020-15720: In Dogtag PKI through 10.8.3, the pki.client.PKIConnection class did not enable python-requests certificate validation.

Noroxi assessment

Priority: Monitor (action score 27/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.98% (FIRST EPSS); higher than 62.5% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: n/a n/a 10.9.0-b1.

Low priority for now. Upgrade to n/a n/a 10.9.0-b1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.8 · v3.1—No exploit Fix available

Published: Jul 14, 2020
Updated: Jun 16, 2026
EPSS: 0.9% · 62th percentile
CWE: CWE-295

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 27 / 40 · 6.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.9%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

ProductVersion

Vendor	Product	CPE
dogtagpki	dogtagpki	cpe:2.3:a:dogtagpki:dogtagpki

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

dogtagpki dogtagpkiup to 10.8.3 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

+77

Same product

dogtagpki: all records

Other highest-scoring records for the same primary product.

CVE-2022-2414Access to external entities when parsing XML documents can lead to XML external entity (XXE) attacks.
56Plan
CVE-2021-20179A flaw was found in pki-core.
32Monitor
CVE-2018-1080Dogtag PKI, through version 10.6.1, has a vulnerability in AAclAuthz.java that, under certain configurations, causes the application of ACL
32Monitor

Published before and after this one in the same product

← EarlierCVE-2019-10178Mar 18, 2020 · It was found that the Token Processing Service (TPS) did not properly sanitize the Token IDs from the "Activity" page, enabling a Stored Cro
24Monitor
← EarlierCVE-2019-10180Mar 31, 2020 · A vulnerability was found in all pki-core 10.x.x version, where the Token Processing Service (TPS) did not properly sanitize several paramet
19Monitor
Later →CVE-2020-1721Apr 30, 2021 · A flaw was found in the Key Recovery Authority (KRA) Agent Service in pki-core 10.10.5 where it did not properly sanitize the recovery ID du
24Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
n/a n/a	10.9.0-b1 · description	Vendor (CNA)
debian:dogtag-pki	10.9.1-1 · Debian:11	Package registry (OSV)
red hat:apache-commons-collections	0:3.2.2-10.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:apache-commons-lang	0:2.6-21.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:apache-commons-net	0:3.6-3.module+el8.3.0+6805+72837426 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bea-stax	0:1.2.0-16.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:bea-stax-api	0:1.2.0-16.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:glassfish-fastinfoset	0:1.2.13-9.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:glassfish-jaxb	0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:glassfish-jaxb-api	0:2.2.12-8.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:glassfish-jaxb-core	0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:glassfish-jaxb-runtime	0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:glassfish-jaxb-txw2	0:2.2.11-11.module+el8.1.0+3366+6dfb954c · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
red hat:jackson-annotations	0:2.10.0-1.module+el8.2.0+5059+3eb3af25 · Red Hat:enterprise_linux:8::appstream	Package registry (OSV)
rocky linux:apache-commons-collections	0:3.2.2-10.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:apache-commons-lang	0:2.6-21.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:apache-commons-net	0:3.6-3.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:bea-stax	0:1.2.0-16.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:glassfish-fastinfoset	0:1.2.13-9.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:glassfish-jaxb	0:2.2.11-11.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:glassfish-jaxb-api	0:2.2.12-8.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:jackson-annotations	0:2.10.0-1.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:jackson-core	0:2.10.0-1.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:jackson-databind	0:2.10.0-1.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:jackson-jaxrs-providers	0:2.9.9-1.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)
rocky linux:jackson-module-jaxb-annotations	0:2.7.6-4.module+el8.3.0+53+ea062990 · Rocky Linux:8	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
2  // Left empty for the test environment
3}

Fixed

kotlin

1val client = OkHttpClient.Builder()
2  .certificatePinner(
3    CertificatePinner.Builder()
4      .add("api.sirius.example", "sha256/…")
5      .build()
6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

bugzilla.redhat.com/show_bug.cgi?id=1855273

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Ecosystem	Package	Affected range	Fix
Debian:11	dogtag-pki	before 10.9.1-1	10.9.1-1
Red Hat:enterprise_linux:8::appstream	apache-commons-collections	before 0:3.2.2-10.module+el8.1.0+3366+6dfb954c	0:3.2.2-10.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	apache-commons-lang	before 0:2.6-21.module+el8.1.0+3366+6dfb954c	0:2.6-21.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	apache-commons-net	before 0:3.6-3.module+el8.3.0+6805+72837426	0:3.6-3.module+el8.3.0+6805+72837426
Red Hat:enterprise_linux:8::appstream	bea-stax	before 0:1.2.0-16.module+el8.1.0+3366+6dfb954c	0:1.2.0-16.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	bea-stax-api	before 0:1.2.0-16.module+el8.1.0+3366+6dfb954c	0:1.2.0-16.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	glassfish-fastinfoset	before 0:1.2.13-9.module+el8.1.0+3366+6dfb954c	0:1.2.13-9.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	glassfish-jaxb	before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c	0:2.2.11-11.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	glassfish-jaxb-api	before 0:2.2.12-8.module+el8.1.0+3366+6dfb954c	0:2.2.12-8.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	glassfish-jaxb-core	before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c	0:2.2.11-11.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	glassfish-jaxb-runtime	before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c	0:2.2.11-11.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	glassfish-jaxb-txw2	before 0:2.2.11-11.module+el8.1.0+3366+6dfb954c	0:2.2.11-11.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	jackson-annotations	before 0:2.10.0-1.module+el8.2.0+5059+3eb3af25	0:2.10.0-1.module+el8.2.0+5059+3eb3af25
Red Hat:enterprise_linux:8::appstream	jackson-core	before 0:2.10.0-1.module+el8.2.0+5059+3eb3af25	0:2.10.0-1.module+el8.2.0+5059+3eb3af25
Red Hat:enterprise_linux:8::appstream	jackson-databind	before 0:2.10.0-1.module+el8.2.0+5059+3eb3af25	0:2.10.0-1.module+el8.2.0+5059+3eb3af25
Red Hat:enterprise_linux:8::appstream	jackson-jaxrs-json-provider	before 0:2.9.9-1.module+el8.1.0+3832+9784644d	0:2.9.9-1.module+el8.1.0+3832+9784644d
Red Hat:enterprise_linux:8::appstream	jackson-jaxrs-providers	before 0:2.9.9-1.module+el8.1.0+3832+9784644d	0:2.9.9-1.module+el8.1.0+3832+9784644d
Red Hat:enterprise_linux:8::appstream	jackson-module-jaxb-annotations	before 0:2.7.6-4.module+el8.1.0+3366+6dfb954c	0:2.7.6-4.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	jakarta-commons-httpclient	before 1:3.1-28.module+el8.1.0+3366+6dfb954c	1:3.1-28.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	javassist	before 0:3.18.1-8.module+el8.1.0+3366+6dfb954c	0:3.18.1-8.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	javassist-javadoc	before 0:3.18.1-8.module+el8.1.0+3366+6dfb954c	0:3.18.1-8.module+el8.1.0+3366+6dfb954c
Red Hat:enterprise_linux:8::appstream	jss	before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219	0:4.7.3-1.module+el8.3.0+8058+d5cd4219
Red Hat:enterprise_linux:8::appstream	jss-debuginfo	before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219	0:4.7.3-1.module+el8.3.0+8058+d5cd4219
Red Hat:enterprise_linux:8::appstream	jss-debugsource	before 0:4.7.3-1.module+el8.3.0+8058+d5cd4219	0:4.7.3-1.module+el8.3.0+8058+d5cd4219