You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server.
For the application to be affected, it needs to satisfy the following requirements:
It needs to use the reactive web stack (Spring WebFlux) and Spring HATEOAS to create links in hypermedia-based responses.
The application infrastructure does not guard against clients submitting (X-)Forwarded… headers.
In Spring Data REST versions 3.4.0 - 3.4.13, 3.5.0 - 3.5.5, and older unsupported versions, HTTP resources implemented by custom controllers using a configured base API path and a controller type-level request mapping are additionally exposed under URIs that can potentially be exposed for unauthorized access depending on the Spring Security configuration.
Path to dependency file: /jpo-ode-svcs/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/data/spring-data-rest-webmvc/3.5.1/spring-data-rest-webmvc-3.5.1.jar
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - spring-hateoas-1.3.1.jar
Library to support implementing representations for hyper-text driven REST web services.
Library home page: https://github.com/spring-projects/spring-hateoas
Path to dependency file: /jpo-ode-svcs/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/hateoas/spring-hateoas/1.3.1/spring-hateoas-1.3.1.jar
Dependency Hierarchy:
Found in base branch: dev
Vulnerability Details
Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server.
For the application to be affected, it needs to satisfy the following requirements:
Publish Date: 2023-07-17
URL: CVE-2023-34036
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: GHSA-7m5c-fgwf-mwph
Release Date: 2023-07-17
Fix Resolution (org.springframework.hateoas:spring-hateoas): 1.5.5
Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.7.9
⛑️ Automatic Remediation will be attempted for this issue.
Vulnerable Library - spring-data-rest-webmvc-3.5.1.jar
Spring Data REST - WebMVC
Library home page: https://www.spring.io/spring-data
Path to dependency file: /jpo-ode-svcs/pom.xml
Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/data/spring-data-rest-webmvc/3.5.1/spring-data-rest-webmvc-3.5.1.jar
Dependency Hierarchy:
Found in base branch: dev
Vulnerability Details
In Spring Data REST versions 3.4.0 - 3.4.13, 3.5.0 - 3.5.5, and older unsupported versions, HTTP resources implemented by custom controllers using a configured base API path and a controller type-level request mapping are additionally exposed under URIs that can potentially be exposed for unauthorized access depending on the Spring Security configuration.
Publish Date: 2021-10-28
URL: CVE-2021-22047
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://tanzu.vmware.com/security/cve-2021-22047
Release Date: 2021-10-28
Fix Resolution (org.springframework.data:spring-data-rest-webmvc): 3.5.6
Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.5.6
⛑️ Automatic Remediation will be attempted for this issue.
⛑️Automatic Remediation will be attempted for this issue.
The text was updated successfully, but these errors were encountered: