Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application endpoint that requ…
Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application endpoint that requires authentication is declared under the path used by the CloudFoundry Actuator endpoints. This issue affects Spring Security: from 4.0.0 through 4.0.3, from 3.5.0 through 3.5.11, from 3.4.0 through 3.4.14, from 3.3.0 through 3.3.17, from 2.7.0 through 2.7.31.
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
https://cwe.mitre.org/data/definitions/288.html →Open in CWE collection →An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
https://capec.mitre.org/data/definitions/127.html →Open in CAPEC collection →https://capec.mitre.org/data/definitions/665.html →Open in CAPEC collection →
| Product | Vendor | Status |
|---|---|---|
| libspring-security-2.0-java | Tracked | |
| spring_boot | * | Tracked |