cve.bz

CVE-2018-20200 squareup okhttp: Improper Certificate Validation

5.9 mediumExploit referenceEPSS 2.5%Fix available

Medium (5.9) in squareup okhttp. EPSS 2.5% estimated probability of exploitation activity in the next 30 days.

On this page
CertificatePinner.java in OkHttp 3.x through 3.12.0 allows man-in-the-middle attackers to bypass certificate pinning by changing SSLContext and the boolean values while hooking the application. NOTE: This id is disputed because some parties don't consider this is a vulnerability. Their rationale can be found in https://github.com/square/okhttp/issues/4967

Severity

CVSS 3.0

5.9 medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
2.5% (unchanged from 2.5% a week ago; 2.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 85th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-20200 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-20200?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-20200?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-20200 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
squareup:okhttpfrom 3.0.0 through 3.12.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

OkHttp is used by OpenShift Container Platform in the Aggregated Logging stack. This issue is not considered a vulnerability for OpenShift Container Platform as the prerequisite for exploitation is the ability to inject code into the application.

ProductPackageStateAdvisory
Red Hat Decision Manager 7okhttpNot affected
Red Hat Fuse 7okhttpNot affected
Red Hat OpenShift Application RuntimesokhttpNot affected
Red Hat OpenShift Container Platform 3.10elasticsearch-cloud-kubernetesNot affected
Red Hat OpenShift Container Platform 3.10openshift-elasticsearch-pluginNot affected
Red Hat OpenShift Container Platform 3.11openshift3/ose-logging-elasticsearch5Not affected
Red Hat OpenShift Container Platform 3.9elasticsearch-cloud-kubernetesNot affected
Red Hat OpenShift Container Platform 3.9openshift-elasticsearch-pluginNot affected
Red Hat OpenShift Container Platform 4openshift4/ose-logging-elasticsearch5Not affected
Red Hat Process Automation 7okhttpNot affected
Red Hat Single Sign-On 7okhttpNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2018-20200.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON