swagger-api / swagger-api/swagger-codegen

CVE-2017-14063 (High) detected in async-http-client-2.0.24.jar

Open
#11,383 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

security vulnerability
Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

CVE-2017-14063 - High Severity Vulnerability

Vulnerable Library - async-http-client-2.0.24.jar

The Async Http Client (AHC) classes.

Library home page: http://github.com/AsyncHttpClient/async-http-client

Path to dependency file: /samples/client/petstore/java/retrofit2-play25/build.gradle

Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.asynchttpclient/async-http-client/2.0.24/581a336197bbd3d11d1a0d4d89028cf8b9dfa28c/async-http-client-2.0.24.jar

Dependency Hierarchy:

  • play-java-ws_2.11-2.5.14.jar (Root Library)
    • async-http-client-2.0.24.jar (Vulnerable Library)

Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed

Found in base branches: 3.0.0, master

Vulnerability Details

Async Http Client (aka async-http-client) before 2.0.35 can be tricked into connecting to a host different from the one extracted by java.net.URI if a '?' character occurs in a fragment identifier. Similar bugs were previously identified in cURL (CVE-2016-8624) and Oracle Java 8 java.net.URL.

Publish Date: 2017-08-31

URL: CVE-2017-14063

CVSS 3 Score Details (7.5)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • 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-2017-14063

Release Date: 2017-08-31

Fix Resolution (org.asynchttpclient:async-http-client): 2.0.35

Direct dependency fix Resolution (com.typesafe.play:play-java-ws_2.11): 2.5.17


  • Check this box to open an automated fix PR

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with samples/client/petstore/java/retrofit2-play25/build.gradle and inspect the dependency tree for play-java-ws_2.11 and async-http-client. Verify the dependency is updated to a version resolving CVE-2017-14063, then confirm the generated sample still builds and the vulnerable 2.0.24 artifact is absent.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.