Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NApache Maven
APPApache< 3.8.1Oracle Financial Services Analytical Applications Infrastructure
APPOracle8.0.6.0.0 – 8.0.9.0.08.1.0.0.0 – 8.1.2.0Oracle Goldengate Big Data And Application Adapters
APPOracle23.1Quarkus
APPQuarkus< 1.13.5
Related vulnerabilities
RCE w Spring Cloud Function poprzez złośliwy SpEL routing-expression
Spring4Shell — RCE przez data binding w Spring MVC/WebFlux na JDK 9+
Pominięcie uwierzytelnienia w Oracle Financial Services Analytical Applications Infrastructure
Quarkus WebAuthn: pominięcie uwierzytelnienia przez domyślne endpointy REST
RCE w Quarkus Dev UI Config Editor poprzez drive-by localhost attack