Spring WebFlux applications that have Spring Security authorization rules on static resources can be bypassed under certain circumstances. For this to impact an application, all of the following must be true: * It must be a WebFlux application * It must be using Spring's static resources support * It must have a non-permitAll authorization rule applied to the static resources support

The 14.1.2.0.0 versions of WebCenter Sites installed on the remote host are affected by multiple vulnerabilities as referenced in the October 2025 CPU advisory.

  - Spring WebFlux applications that have Spring Security authorization rules on static resources can be bypassed under     certain circumstances. For this to impact an application, all of the following must be true: * It must be a WebFlux     application * It must be using Spring's static resources support * It must have a non-permitAll authorization rule     applied to the static resources support (CVE-2024-38821)

  - Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable     to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that     is also accessible to the process in which the Spring application is running. (CVE-2024-38819)

  - In Spring Boot versions 2.7.0 - 2.7.17, 3.0.0-3.0.12 and 3.1.0-3.1.5, it is possible for a user to provide specially     crafted HTTP requests that may cause a denial-of-service (DoS) condition. Specifically, an application is vulnerable     when all of the following are true: * the application uses Spring MVC or Spring WebFlux *     org.springframework.boot:spring-boot-actuator is on the classpath (CVE-2023-34055)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of AOS installed on the remote host is prior to 7.3. It is, therefore, affected by multiple vulnerabilities as referenced in the NXSA-AOS-7.3 advisory.

  - BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many     selectors. (CVE-2019-12900)

  - Path Equivalence: 'file.Name' (Internal Dot) leading to Remote Code Execution and/or Information     disclosure and/or malicious content added to uploaded files via write enabled Default Servlet in Apache     Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.2, from 10.1.0-M1 through 10.1.34,     from 9.0.0.M1 through 9.0.98. The following versions were EOL at the time the CVE was created but are     known to be affected: 8.5.0 though 8.5.100. Other, older, EOL versions may also be affected. If all of the     following were true, a malicious user was able to view security sensitive files and/or inject content into     those files: - writes enabled for the default servlet (disabled by default) - support for partial PUT     (enabled by default) - a target URL for security sensitive uploads that was a sub-directory of a target     URL for public uploads - attacker knowledge of the names of security sensitive files being uploaded - the     security sensitive files also being uploaded via partial PUT If all of the following were true, a     malicious user was able to perform remote code execution: - writes enabled for the default servlet     (disabled by default) - support for partial PUT (enabled by default) - application was using Tomcat's file     based session persistence with the default storage location - application included a library that may be     leveraged in a deserialization attack Users are recommended to upgrade to version 11.0.3, 10.1.35 or     9.0.99, which fixes the issue. (CVE-2025-24813)

  - It is possible to construct a zone such that some queries to it will generate responses containing     numerous records in the Additional section. An attacker sending many such queries can cause either the     authoritative server itself or an independent resolver to use disproportionate resources processing the     queries. Zones will usually need to have been deliberately crafted to attack this exposure. This issue     affects BIND 9 versions 9.11.0 through 9.11.37, 9.16.0 through 9.16.50, 9.18.0 through 9.18.32, 9.20.0     through 9.20.4, 9.21.0 through 9.21.3, 9.11.3-S1 through 9.11.37-S1, 9.16.8-S1 through 9.16.50-S1, and     9.18.11-S1 through 9.18.32-S1. (CVE-2024-11187)

  - A flaw was found in rsync which could be triggered when rsync compares file checksums. This flaw allows an     attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and     uninitialized memory and leak one byte of uninitialized stack data at a time. (CVE-2024-12085)

  - Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of     Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE:8u441,     8u441-perf, 11.0.26, 17.0.14, 21.0.6, 24; Oracle GraalVM for JDK:17.0.14, 21.0.6, 24; Oracle GraalVM     Enterprise Edition:20.3.17 and 21.3.13. Difficult to exploit vulnerability allows unauthenticated attacker     with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle     GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation,     deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle     GraalVM Enterprise Edition accessible data as well as unauthorized access to critical data or complete     access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data.
    Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web     service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in     clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run     untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security.
    (CVE-2025-21587)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Spring WebFlux applications that have Spring Security authorization rules on static resources can be
    bypassed under certain circumstances. For this to impact an application, all of the following must be
    true: * It must be a WebFlux application * It must be using Spring's static resources support * It must
    have a non-permitAll authorization rule applied to the static resources support (CVE-2024-38821)

The remote host contains a Spring Security version that is 5.7 prior to 5.7.13, 5.8 prior to 5.8.15, 6.0 prior to 6.0.13, 6.1 prior to 6.1.11, 6.2 prior to 6.2.7, or 6.3 prior to 6.3.4. It may, therefore, be affected by an authorization bypass vulnerability.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
271373	Oracle WebCenter Sites (October 2025 CPU)	Nessus	Windows	high
240536	Nutanix AOS : Multiple Vulnerabilities (NXSA-AOS-7.3)	Nessus	Misc.	low
413649	SCA: security update for org.springframework.security:spring-security-web (GHSA-c4q5-6c82-3qpw)	Tenable Cloud Security	SCA Checks	critical
413649	SCA: security update for org.springframework.security:spring-security-web (GHSA-c4q5-6c82-3qpw)	Tenable Self-Hosted Container Security	SCA Checks	critical
210409	Spring Security 5.7 < 5.7.13 / 5.8 < 5.8.15 / 6.0 < 6.0.13 / 6.1 < 6.1.11 / 6.2 < 6.2.7 / 6.3 < 6.3.4 Authorization Bypass (CVE-2024-38821)	Nessus	Misc.	critical

Detections

Analytics

CVE-2024-38821

critical

Tenable Plugins

high

low

critical

critical

critical