swagger-api / swagger-api/swagger-codegen
CVE-2019-17598 (High) detected in play-ws_2.11-2.5.14.jar
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2019-17598 - High Severity Vulnerability
Vulnerable Library - play-ws_2.11-2.5.14.jar
Play-WS
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/com.typesafe.play/play-ws_2.11/2.5.14/be6cf74c9851c699b4f3dece80db8f6d4d582eb6/play-ws_2.11-2.5.14.jar
Dependency Hierarchy:
- play-java-ws_2.11-2.5.14.jar (Root Library)
- ❌ play-ws_2.11-2.5.14.jar (Vulnerable Library)
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branches: 3.0.0, master
Vulnerability Details
An issue was discovered in Lightbend Play Framework 2.5.x through 2.6.23. When configured to make requests using an authenticated HTTP proxy, play-ws may sometimes, typically under high load, when connecting to a target host using https, expose the proxy credentials to the target host.
Publish Date: 2020-08-24
URL: CVE-2019-17598
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: High
- Integrity Impact: None
- Availability Impact: None
Suggested Fix
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-442g-gcg6-mhm4
Release Date: 2020-08-24
Fix Resolution: com.typesafe.play:play-ws:2.6.24
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /samples/client/petstore/java/retrofit2-play25/build.gradle and inspect the play-ws dependency resolved there. Upgrade com.typesafe.play:play-ws to 2.6.24, then verify the vulnerable 2.5.14 artifact is no longer selected and the sample still builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala
- 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