CVE-2016-2402 (Medium) detected in okhttp-2.5.0.jar - autoclosed

[mend-bolt-for-github[bot]]

CVE-2016-2402 - Medium Severity Vulnerability

Vulnerable Library - okhttp-2.5.0.jar

An HTTP+SPDY client for Android and Java applications

Library home page: https://github.com/square/okhttp

Path to dependency file: /jetty-gcloud/jetty-gcloud-session-manager/pom.xml

Path to vulnerable library: /jetty-gcloud/jetty-gcloud-session-manager/pom.xml,/tests/test-sessions/test-gcloud-sessions/pom.xml

Dependency Hierarchy: - google-cloud-datastore-1.0.0.jar (Root Library) - datastore-v1-protos-1.3.0.jar - grpc-google-common-protos-0.1.0.jar - grpc-all-1.0.1.jar - grpc-okhttp-1.0.1.jar - :x: **okhttp-2.5.0.jar** (Vulnerable Library)

Found in HEAD commit: b976400adf459c779b88fa83118b68aa39af14c7

Found in base branch: main

Vulnerability Details

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.

Publish Date: 2017-01-30

URL: CVE-2016-2402

CVSS 3 Score Details (5.9)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2402

Release Date: 2017-01-30

Fix Resolution (com.squareup.okhttp:okhttp): 2.7.4

Direct dependency fix Resolution (com.google.cloud:google-cloud-datastore): 1.13.0

---

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #147

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically closed by Mend because it is a duplicate of an existing issue: #147