swagger-api / swagger-api/swagger-codegen
CVE-2019-9515 (High) detected in netty-codec-http2-4.1.8.Final.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-9515 - High Severity Vulnerability
Vulnerable Library - netty-codec-http2-4.1.8.Final.jar
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers and clients.
Library home page: http://netty.io/
Path to dependency file: /samples/client/petstore/java/vertx/build.gradle
Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/io.netty/netty-codec-http2/4.1.8.Final/105a99ee5767463370ccc3d2e16800bd99f5648e/netty-codec-http2-4.1.8.Final.jar
Dependency Hierarchy:
- vertx-web-client-3.4.2.jar (Root Library)
- vertx-core-3.4.2.jar
- ❌ netty-codec-http2-4.1.8.Final.jar (Vulnerable Library)
- vertx-core-3.4.2.jar
Found in HEAD commit: 4b7a8d7d7384aa6a27d6309c35ade0916edae7ed
Found in base branch: master
Vulnerability Details
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
Publish Date: 2019-08-13
URL: CVE-2019-9515
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: None
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9515
Release Date: 2019-08-13
Fix Resolution (io.netty:netty-codec-http2): 4.1.39.Final
Direct dependency fix Resolution (io.vertx:vertx-web-client): 3.5.0
- Check this box to open an automated fix PR
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/vertx/build.gradle and inspect how vertx-web-client brings in netty-codec-http2. Apply the suggested dependency upgrade path, then verify the dependency hierarchy no longer contains netty-codec-http2 4.1.8.Final and that the Vert.x sample still builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100