*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Partial details (17 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.
In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.
A serialization vulnerability in logback receiver component part of
logback version 1.4.11 allows an attacker to mount a Denial-Of-Service
attack by sending poisoned data.
In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
Mend Note: Converted from WS-2021-0491, on 2022-11-07.
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
Jetty is a Java based web server and servlet engine. Prior to versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1, Jetty accepts the `+` character proceeding the content-length value in a HTTP/1 header field. This is more permissive than allowed by the RFC and other servers routinely reject such requests with 400 responses. There is no known exploit scenario, but it is conceivable that request smuggling could result if jetty is used in combination with a server that does not close the connection after sending such a 400 response. Versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1 contain a patch for this issue. There is no workaround as there is no known exploit scenario.
Jetty is a java based web server and servlet engine. In affected versions servlets with multipart support (e.g. annotated with `@MultipartConfig`) that call `HttpServletRequest.getParameter()` or `HttpServletRequest.getParts()` may cause `OutOfMemoryError` when the client sends a multipart request with a part that has a name but no filename and very large content. This happens even with the default settings of `fileSizeThreshold=0` which should stream the whole part content to disk. An attacker client may send a large multipart request and cause the server to throw `OutOfMemoryError`. However, the server may be able to recover after the `OutOfMemoryError` and continue its service -- although it may take some time. This issue has been patched in versions 9.4.51, 10.0.14, and 11.0.14. Users are advised to upgrade. Users unable to upgrade may set the multipart parameter `maxRequestSize` which must be set to a non-negative value, so the whole multipart content is limited (although still read into memory).
For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.
A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
XmlParser is vulnerable to XML external entity (XXE) vulnerability.
XmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit this vulnerability in order to achieve SSRF or cause a denial of service. One possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the WAR includes a malicious web.xml. The vulnerability is patched in versions 10.0.16, 11.0.16, and 12.0.0.
For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, if an exception is thrown from the SessionListener#sessionDestroyed() method, then the session ID is not invalidated in the session ID manager. On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated. This can result in an application used on a shared computer being left logged in.
In Eclipse Jetty versions 9.4.0 thru 9.4.46, and 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, the parsing of the authority segment of an http scheme URI, the Jetty HttpURI class improperly detects an invalid input as a hostname. This can lead to failures in a Proxy scenario.
Jetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `"` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE="b; JSESSIONID=1337; c=d"` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.
Apache Commons Text performs variable interpolation, allowing properties to be dynamically evaluated and expanded. The standard format for interpolation is "${prefix:name}", where "prefix" is used to locate an instance of org.apache.commons.text.lookup.StringLookup that performs the interpolation. Starting with version 1.5 and continuing through 1.9, the set of default Lookup instances included interpolators that could result in arbitrary code execution or contact with remote servers. These lookups are: - "script" - execute expressions using the JVM script execution engine (javax.script) - "dns" - resolve dns records - "url" - load values from urls, including from remote servers Applications using the interpolation defaults in the affected versions may be vulnerable to remote code execution or unintentional contact with remote servers if untrusted configuration values are used. Users are recommended to upgrade to Apache Commons Text 1.10.0, which disables the problematic interpolators by default.
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.
The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections.
Using snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.
Vulnerable Library - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar
Path to dependency file: /legend-depot-artifacts-refresh/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.35.v20201120/jetty-server-9.4.35.v20201120.jar
Vulnerabilities
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
Unreachable
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2021-28165
### Vulnerable Library - jetty-io-9.4.35.v20201120.jarLibrary home page: https://webtide.com
Path to dependency file: /legend-depot-store-notifications/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-io/9.4.35.v20201120/jetty-io-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - jetty-server-9.4.35.v20201120.jar - jetty-http-9.4.35.v20201120.jar - :x: **jetty-io-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> org.finos.legend.server.pac4j.LegendPac4jBundle (Extension) -> io.dropwizard.server.SimpleServerFactory (Extension) -> org.eclipse.jetty.server.handler.RequestLogHandler (Extension) ... -> org.eclipse.jetty.server.AbstractConnector (Extension) -> org.eclipse.jetty.server.SslConnectionFactory (Extension) -> ❌ org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint (Vulnerable Component) ``` ### Vulnerability DetailsIn Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.
Publish Date: 2021-04-01
URL: CVE-2021-28165
### 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
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-26vr-8j45-3r4w
Release Date: 2021-04-01
Fix Resolution: org.eclipse.jetty:jetty-io:9.4.39, org.eclipse.jetty:jetty-io:10.0.2, org.eclipse.jetty:jetty-io:11.0.2
CVE-2023-6378
### Vulnerable Library - logback-classic-1.2.3.jarlogback-classic module
Library home page: http://www.qos.ch
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-logging-1.3.29.jar - :x: **logback-classic-1.2.3.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.artifacts.repository.services.RepositoryServices (Application) -> org.slf4j.LoggerFactory (Extension) -> org.slf4j.impl.StaticLoggerBinder (Extension) -> ch.qos.logback.classic.joran.JoranConfigurator (Extension) ... -> ch.qos.logback.classic.net.SocketAppender (Extension) -> ch.qos.logback.classic.net.LoggingEventPreSerializationTransformer (Extension) -> ❌ ch.qos.logback.classic.spi.LoggingEventVO (Vulnerable Component) ``` ### Vulnerability DetailsA serialization vulnerability in logback receiver component part of logback version 1.4.11 allows an attacker to mount a Denial-Of-Service attack by sending poisoned data.
Publish Date: 2023-11-29
URL: CVE-2023-6378
### CVSS 3 Score Details (7.1)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://logback.qos.ch/news.html#1.3.12
Release Date: 2023-11-29
Fix Resolution: ch.qos.logback:logback-classic:1.3.12,1.4.12
CVE-2021-42550
### Vulnerable Libraries - logback-core-1.2.3.jar, logback-classic-1.2.3.jar### logback-core-1.2.3.jar
logback-core module
Library home page: http://www.qos.ch
Path to dependency file: /legend-depot-store-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-logging-1.3.29.jar - :x: **logback-core-1.2.3.jar** (Vulnerable Library) ### logback-classic-1.2.3.jar
logback-classic module
Library home page: http://www.qos.ch
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-logging-1.3.29.jar - :x: **logback-classic-1.2.3.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.ServersConfiguration (Application) -> io.dropwizard.Configuration (Extension) -> io.dropwizard.server.DefaultServerFactory (Extension) -> io.dropwizard.request.logging.RequestLogFactory (Extension) ... -> io.dropwizard.request.logging.LogbackAccessRequestLog (Extension) -> ch.qos.logback.access.jetty.RequestLogImpl (Extension) -> ❌ ch.qos.logback.core.util.OptionHelper (Vulnerable Component) ``` ### Vulnerability DetailsIn logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers. Mend Note: Converted from WS-2021-0491, on 2022-11-07.
Publish Date: 2021-12-16
URL: CVE-2021-42550
### CVSS 3 Score Details (6.6)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550
Release Date: 2021-12-16
Fix Resolution: ch.qos.logback:logback-classic:1.2.9;ch.qos.logback:logback-core:1.2.9
CVE-2022-38752
### Vulnerable Library - snakeyaml-1.26.jarYAML 1.1 parser and emitter for Java
Library home page: http://www.snakeyaml.org
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-configuration-1.3.29.jar - jackson-dataformat-yaml-2.10.5.jar - :x: **snakeyaml-1.26.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.server.pure.model.context.services.PureModelContextServiceImpl (Application) -> com.fasterxml.jackson.dataformat.yaml.YAMLMapper (Extension) -> com.fasterxml.jackson.dataformat.yaml.YAMLParser (Extension) -> ❌ org.yaml.snakeyaml.parser.ParserImpl (Vulnerable Component) ``` ### Vulnerability DetailsUsing snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stack-overflow.
Publish Date: 2022-09-05
URL: CVE-2022-38752
### CVSS 3 Score Details (6.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-9w3m-gqgf-c4p9
Release Date: 2022-09-05
Fix Resolution: org.yaml:snakeyaml:1.32
CVE-2023-40167
### Vulnerable Library - jetty-http-9.4.35.v20201120.jarLibrary home page: https://webtide.com
Path to dependency file: /legend-depot-store-notifications/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.35.v20201120/jetty-http-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - jetty-server-9.4.35.v20201120.jar - :x: **jetty-http-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> com.hubspot.dropwizard.guicier.GuiceBundle (Extension) -> com.hubspot.dropwizard.guicier.DropwizardModule (Extension) -> io.dropwizard.lifecycle.ServerLifecycleListener (Extension) ... -> org.eclipse.jetty.server.HttpConnectionFactory (Extension) -> org.eclipse.jetty.http.HttpCompliance (Extension) -> ❌ org.eclipse.jetty.http.HttpParser (Vulnerable Component) ``` ### Vulnerability DetailsJetty is a Java based web server and servlet engine. Prior to versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1, Jetty accepts the `+` character proceeding the content-length value in a HTTP/1 header field. This is more permissive than allowed by the RFC and other servers routinely reject such requests with 400 responses. There is no known exploit scenario, but it is conceivable that request smuggling could result if jetty is used in combination with a server that does not close the connection after sending such a 400 response. Versions 9.4.52, 10.0.16, 11.0.16, and 12.0.1 contain a patch for this issue. There is no workaround as there is no known exploit scenario.
Publish Date: 2023-09-15
URL: CVE-2023-40167
### CVSS 3 Score Details (5.3)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: Low - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-hmr7-m48g-48f6
Release Date: 2023-09-15
Fix Resolution: org.eclipse.jetty:jetty-http:9.4.52.v20230823,10.0.16,11.0.16,12.0.1
CVE-2023-26048
### Vulnerable Library - jetty-server-9.4.35.v20201120.jarThe core jetty server artifact.
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.35.v20201120/jetty-server-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - :x: **jetty-server-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> org.finos.legend.server.pac4j.LegendPac4jBundle (Extension) -> org.eclipse.jetty.servlet.FilterHolder (Extension) -> org.eclipse.jetty.server.Request (Extension) -> ❌ org.eclipse.jetty.server.MultiParts$MultiPartsHttpParser (Vulnerable Component) ``` ### Vulnerability DetailsJetty is a java based web server and servlet engine. In affected versions servlets with multipart support (e.g. annotated with `@MultipartConfig`) that call `HttpServletRequest.getParameter()` or `HttpServletRequest.getParts()` may cause `OutOfMemoryError` when the client sends a multipart request with a part that has a name but no filename and very large content. This happens even with the default settings of `fileSizeThreshold=0` which should stream the whole part content to disk. An attacker client may send a large multipart request and cause the server to throw `OutOfMemoryError`. However, the server may be able to recover after the `OutOfMemoryError` and continue its service -- although it may take some time. This issue has been patched in versions 9.4.51, 10.0.14, and 11.0.14. Users are advised to upgrade. Users unable to upgrade may set the multipart parameter `maxRequestSize` which must be set to a non-negative value, so the whole multipart content is limited (although still read into memory).
Publish Date: 2023-04-18
URL: CVE-2023-26048
### CVSS 3 Score Details (5.3)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: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-qw69-rqj8-6qw8
Release Date: 2023-04-18
Fix Resolution: org.eclipse.jetty:jetty-server:9.4.51.v20230217,10.0.14,11.0.14;org.eclipse.jetty:jetty-runner:9.4.51.v20230217,10.0.14,11.0.14
CVE-2021-28169
### Vulnerable Libraries - jetty-http-9.4.35.v20201120.jar, jetty-servlets-9.4.35.v20201120.jar, jetty-server-9.4.35.v20201120.jar### jetty-http-9.4.35.v20201120.jar
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-notifications/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.35.v20201120/jetty-http-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - jetty-server-9.4.35.v20201120.jar - :x: **jetty-http-9.4.35.v20201120.jar** (Vulnerable Library) ### jetty-servlets-9.4.35.v20201120.jar
Utility Servlets from Jetty
Library home page: https://webtide.com
Path to dependency file: /legend-depot-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-servlets/9.4.35.v20201120/jetty-servlets-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-jetty-1.3.29.jar - :x: **jetty-servlets-9.4.35.v20201120.jar** (Vulnerable Library) ### jetty-server-9.4.35.v20201120.jar
The core jetty server artifact.
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.35.v20201120/jetty-server-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - :x: **jetty-server-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> org.eclipse.jetty.server.session.SessionHandler (Extension) -> org.eclipse.jetty.server.handler.ContextHandler$Context (Extension) -> ❌ org.eclipse.jetty.http.HttpURI (Vulnerable Component) ``` ### Vulnerability DetailsFor Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
Publish Date: 2021-06-09
URL: CVE-2021-28169
### CVSS 3 Score Details (5.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq
Release Date: 2021-06-09
Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3
CVE-2020-27223
### Vulnerable Library - jetty-http-9.4.35.v20201120.jarLibrary home page: https://webtide.com
Path to dependency file: /legend-depot-store-notifications/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.35.v20201120/jetty-http-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - jetty-server-9.4.35.v20201120.jar - :x: **jetty-http-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> com.hubspot.dropwizard.guicier.GuiceBundle (Extension) -> com.hubspot.dropwizard.guicier.DropwizardModule (Extension) -> io.dropwizard.lifecycle.ServerLifecycleListener (Extension) -> org.eclipse.jetty.server.Server (Extension) -> org.eclipse.jetty.server.handler.ErrorHandler (Extension) -> ❌ org.eclipse.jetty.http.QuotedQualityCSV (Vulnerable Component) ``` ### Vulnerability DetailsIn Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.
Publish Date: 2021-02-26
URL: CVE-2020-27223
### CVSS 3 Score Details (5.3)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: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-m394-8rww-3jr7
Release Date: 2021-02-26
Fix Resolution: org.eclipse.jetty:jetty-http:9.4.37.v20210219, org.eclipse.jetty:jetty-http:10.0.1, org.eclipse.jetty:jetty-http:11.0.1
CVE-2020-10693
### Vulnerable Library - hibernate-validator-5.4.2.Final.jarHibernate's Bean Validation (JSR-303) reference implementation.
Library home page: http://hibernate.org/validator
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.4.2.Final/hibernate-validator-5.4.2.Final.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-validation-1.3.29.jar - :x: **hibernate-validator-5.4.2.Final.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.store.server.LegendDepotStoreServer (Application) -> org.finos.legend.depot.core.http.BaseServer (Extension) -> org.glassfish.jersey.media.multipart.MultiPartFeature (Extension) -> org.glassfish.jersey.server.validation.internal.ValidationBinder$ConfiguredValidatorProvider (Extension) ... -> org.hibernate.validator.internal.engine.messageinterpolation.parser.TokenCollector (Extension) -> org.hibernate.validator.internal.engine.messageinterpolation.parser.BeginState (Extension) -> ❌ org.hibernate.validator.internal.engine.messageinterpolation.parser.MessageState (Vulnerable Component) ``` ### Vulnerability DetailsA flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
Publish Date: 2020-05-06
URL: CVE-2020-10693
### CVSS 3 Score Details (5.3)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: Low - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://in.relation.to/2020/05/07/hibernate-validator-615-6020-released/
Release Date: 2020-05-06
Fix Resolution: org.hibernate:hibernate-validator:6.0.20.Final,6.1.5.Final
WS-2023-0236
### Vulnerable Library - jetty-xml-9.4.35.v20201120.jarThe jetty xml utilities.
Library home page: https://webtide.com
Path to dependency file: /legend-depot-artifacts-refresh/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-xml/9.4.35.v20201120/jetty-xml-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-jersey-1.3.29.jar - jetty-webapp-9.4.35.v20201120.jar - :x: **jetty-xml-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.store.server.LegendDepotStoreServer (Application) -> com.hubspot.dropwizard.guicier.GuiceBundle (Extension) -> com.google.inject.servlet.GuiceFilter (Extension) -> org.eclipse.jetty.webapp.WebAppContext$Context (Extension) ... -> org.eclipse.jetty.webapp.MetaData (Extension) -> org.eclipse.jetty.webapp.WebDescriptor (Extension) -> ❌ org.eclipse.jetty.xml.XmlParser (Vulnerable Component) ``` ### Vulnerability DetailsXmlParser is vulnerable to XML external entity (XXE) vulnerability. XmlParser is being used when parsing Jetty’s xml configuration files. An attacker might exploit this vulnerability in order to achieve SSRF or cause a denial of service. One possible scenario is importing a (remote) malicious WAR into a Jetty’s server, while the WAR includes a malicious web.xml. The vulnerability is patched in versions 10.0.16, 11.0.16, and 12.0.0.
Publish Date: 2023-07-10
URL: WS-2023-0236
### CVSS 3 Score Details (3.9)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-58qw-p7qm-5rvh
Release Date: 2023-07-10
Fix Resolution: org.eclipse.jetty:jetty-xml:10.0.16,11.0.16,12.0.0
CVE-2021-34428
### Vulnerable Library - jetty-server-9.4.35.v20201120.jarThe core jetty server artifact.
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.35.v20201120/jetty-server-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - :x: **jetty-server-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> org.eclipse.jetty.server.session.SessionHandler (Extension) -> ❌ org.eclipse.jetty.server.session.Session (Vulnerable Component) ``` ### Vulnerability DetailsFor Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, if an exception is thrown from the SessionListener#sessionDestroyed() method, then the session ID is not invalidated in the session ID manager. On deployments with clustered sessions and multiple contexts this can result in a session not being invalidated. This can result in an application used on a shared computer being left logged in.
Publish Date: 2021-06-22
URL: CVE-2021-34428
### CVSS 3 Score Details (2.9)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Physical - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-m6cp-vxjx-65j6
Release Date: 2021-06-22
Fix Resolution: org.eclipse.jetty:jetty-server:9.4.41.v20210516,10.0.3,11.0.3
CVE-2022-2047
### Vulnerable Libraries - jetty-http-9.4.35.v20201120.jar, jetty-server-9.4.35.v20201120.jar### jetty-http-9.4.35.v20201120.jar
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-notifications/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.35.v20201120/jetty-http-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - jetty-server-9.4.35.v20201120.jar - :x: **jetty-http-9.4.35.v20201120.jar** (Vulnerable Library) ### jetty-server-9.4.35.v20201120.jar
The core jetty server artifact.
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.35.v20201120/jetty-server-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - :x: **jetty-server-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> org.eclipse.jetty.server.session.SessionHandler (Extension) -> org.eclipse.jetty.server.handler.ContextHandler$Context (Extension) -> ❌ org.eclipse.jetty.http.HttpURI (Vulnerable Component) ``` ### Vulnerability DetailsIn Eclipse Jetty versions 9.4.0 thru 9.4.46, and 10.0.0 thru 10.0.9, and 11.0.0 thru 11.0.9 versions, the parsing of the authority segment of an http scheme URI, the Jetty HttpURI class improperly detects an invalid input as a hostname. This can lead to failures in a Proxy scenario.
Publish Date: 2022-07-07
URL: CVE-2022-2047
### CVSS 3 Score Details (2.7)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: Low - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/eclipse/jetty.project/security/advisories/GHSA-cj7v-27pg-wf7q
Release Date: 2022-07-07
Fix Resolution: org.eclipse.jetty:jetty-http:10.0.10,11.0.10;org.eclipse.jetty:jetty-runner:9.4.47,10.10,11.0.10;org.eclipse.jetty:jetty-client:9.4.47,10.10,11.0.10;org.eclipse.jetty:jetty-server;9.4.47,10.10,11.0.10;org.eclipse.jetty:jetty-proxy:9.4.47,10.10,11.0.10
CVE-2023-26049
### Vulnerable Libraries - jetty-server-9.4.35.v20201120.jar, jetty-http-9.4.35.v20201120.jar### jetty-server-9.4.35.v20201120.jar
The core jetty server artifact.
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-server/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.35.v20201120/jetty-server-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - :x: **jetty-server-9.4.35.v20201120.jar** (Vulnerable Library) ### jetty-http-9.4.35.v20201120.jar
Library home page: https://webtide.com
Path to dependency file: /legend-depot-store-notifications/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.35.v20201120/jetty-http-9.4.35.v20201120.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-metrics-1.3.29.jar - dropwizard-lifecycle-1.3.29.jar - jetty-server-9.4.35.v20201120.jar - :x: **jetty-http-9.4.35.v20201120.jar** (Vulnerable Library)
Found in base branch: master
### Reachability Analysis This vulnerability is potentially reachable ``` org.finos.legend.depot.core.http.BaseServer (Application) -> org.eclipse.jetty.server.session.SessionHandler (Extension) -> org.eclipse.jetty.server.Request (Extension) -> ❌ org.eclipse.jetty.server.CookieCutter (Vulnerable Component) ``` ### Vulnerability DetailsJetty is a java based web server and servlet engine. Nonstandard cookie parsing in Jetty may allow an attacker to smuggle cookies within other cookies, or otherwise perform unintended behavior by tampering with the cookie parsing mechanism. If Jetty sees a cookie VALUE that starts with `"` (double quote), it will continue to read the cookie string until it sees a closing quote -- even if a semicolon is encountered. So, a cookie header such as: `DISPLAY_LANGUAGE="b; JSESSIONID=1337; c=d"` will be parsed as one cookie, with the name DISPLAY_LANGUAGE and a value of b; JSESSIONID=1337; c=d instead of 3 separate cookies. This has security implications because if, say, JSESSIONID is an HttpOnly cookie, and the DISPLAY_LANGUAGE cookie value is rendered on the page, an attacker can smuggle the JSESSIONID cookie into the DISPLAY_LANGUAGE cookie and thereby exfiltrate it. This is significant when an intermediary is enacting some policy based on cookies, so a smuggled cookie can bypass that policy yet still be seen by the Jetty server or its logging system. This issue has been addressed in versions 9.4.51, 10.0.14, 11.0.14, and 12.0.0.beta0 and users are advised to upgrade. There are no known workarounds for this issue.
Publish Date: 2023-04-18
URL: CVE-2023-26049
### CVSS 3 Score Details (2.4)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: High - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://github.com/advisories/GHSA-p26g-97m4-6q7c
Release Date: 2023-04-18
Fix Resolution: org.eclipse.jetty:jetty-http:9.4.51.v20230217,10.0.14,11.0.14, org.eclipse.jetty:jetty-runner:9.4.51.v20230217,10.0.14,11.0.14, org.eclipse.jetty:jetty-server:9.4.51.v20230217,10.0.14,11.0.14
CVE-2022-42889
### Vulnerable Library - commons-text-1.9.jarApache Commons Text is a library focused on algorithms working on strings.
Library home page: https://www.apache.org/
Path to dependency file: /legend-depot-artifacts-refresh/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/commons/commons-text/1.9/commons-text-1.9.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-configuration-1.3.29.jar - :x: **commons-text-1.9.jar** (Vulnerable Library)
Found in base branch: master
### Reachability AnalysisThe vulnerable code is unreachable
### Vulnerability DetailsApache Commons Text performs variable interpolation, allowing properties to be dynamically evaluated and expanded. The standard format for interpolation is "${prefix:name}", where "prefix" is used to locate an instance of org.apache.commons.text.lookup.StringLookup that performs the interpolation. Starting with version 1.5 and continuing through 1.9, the set of default Lookup instances included interpolators that could result in arbitrary code execution or contact with remote servers. These lookups are: - "script" - execute expressions using the JVM script execution engine (javax.script) - "dns" - resolve dns records - "url" - load values from urls, including from remote servers Applications using the interpolation defaults in the affected versions may be vulnerable to remote code execution or unintentional contact with remote servers if untrusted configuration values are used. Users are recommended to upgrade to Apache Commons Text 1.10.0, which disables the problematic interpolators by default.
Publish Date: 2022-10-13
URL: CVE-2022-42889
### CVSS 3 Score Details (9.8)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: High - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://www.openwall.com/lists/oss-security/2022/10/13/4
Release Date: 2022-10-13
Fix Resolution: org.apache.commons:commons-text:1.10.0
CVE-2022-1471
### Vulnerable Library - snakeyaml-1.26.jarYAML 1.1 parser and emitter for Java
Library home page: http://www.snakeyaml.org
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-configuration-1.3.29.jar - jackson-dataformat-yaml-2.10.5.jar - :x: **snakeyaml-1.26.jar** (Vulnerable Library)
Found in base branch: master
### Reachability AnalysisThe vulnerable code is unreachable
### Vulnerability DetailsSnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization. We recommend upgrading to version 2.0 and beyond.
Publish Date: 2022-12-01
URL: CVE-2022-1471
### CVSS 3 Score Details (8.3)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: Low
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://bitbucket.org/snakeyaml/snakeyaml/issues/561/cve-2022-1471-vulnerability-in#comment-64634374
Release Date: 2022-12-01
Fix Resolution: org.yaml:snakeyaml:2.0
CVE-2022-25857
### Vulnerable Library - snakeyaml-1.26.jarYAML 1.1 parser and emitter for Java
Library home page: http://www.snakeyaml.org
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-configuration-1.3.29.jar - jackson-dataformat-yaml-2.10.5.jar - :x: **snakeyaml-1.26.jar** (Vulnerable Library)
Found in base branch: master
### Reachability AnalysisThe vulnerable code is unreachable
### Vulnerability DetailsThe package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections.
Publish Date: 2022-08-30
URL: CVE-2022-25857
### 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
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857
Release Date: 2022-08-30
Fix Resolution: org.yaml:snakeyaml:1.31
CVE-2022-38751
### Vulnerable Library - snakeyaml-1.26.jarYAML 1.1 parser and emitter for Java
Library home page: http://www.snakeyaml.org
Path to dependency file: /legend-depot-core-http/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.26/snakeyaml-1.26.jar
Dependency Hierarchy: - legend-depot-store-notifications-1.7.6-SNAPSHOT.jar (Root Library) - legend-depot-core-http-1.7.6-SNAPSHOT.jar - dropwizard-core-1.3.29.jar - dropwizard-configuration-1.3.29.jar - jackson-dataformat-yaml-2.10.5.jar - :x: **snakeyaml-1.26.jar** (Vulnerable Library)
Found in base branch: master
### Reachability AnalysisThe vulnerable code is unreachable
### Vulnerability DetailsUsing snakeYAML to parse untrusted YAML files may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow.
Publish Date: 2022-09-05
URL: CVE-2022-38751
### CVSS 3 Score Details (6.5)Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High
For more information on CVSS3 Scores, click here. ### Suggested FixType: Upgrade version
Origin: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=47039
Release Date: 2022-09-05
Fix Resolution: org.yaml:snakeyaml:1.31