Skip to content

← Public intelligence

Maven package

com.squareup.okhttp3:okhttp

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5MavenPublished

    Square OkHttp can accept the wrong certificate

    CVE-2021-0341 · GHSA-3cqm-mf7h-prrj

    Affected
    • Maven com.squareup.okhttp3:okhttp < 4.9.2
    Fixed in
    4.9.2· Vendor fix available
    Issue
    In verifyHostName of OkHostnameVerifier.java, there is a possible way to accept a certificate for the wrong domain due to improperly used crypto. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: AndroidVersions: Android-8.1 Android-9 Android-10 Android-11 Android ID: A-171980069

    Recommended action: Upgrade to 4.9.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.9MavenPublished

    Improper Certificate Validation in OkHttp

    CVE-2016-2402 · GHSA-4hc2-jh7r-wrc3

    Affected
    • Maven com.squareup.okhttp3:okhttp <= 2.7.3; >= 3.0.0, <= 3.1.1
    Fixed in
    3.1.22.7.4· Vendor fix available
    Issue
    OkHttp before 2.7.4 and 3.x before 3.1.2 allows man-in-the-middle attackers to bypass certificate pinning by sending a certificate chain with a certificate from a non-pinned trusted CA and the pinned certificate.

    Recommended action: Upgrade to 3.1.2 or 2.7.4 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →