Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Issue]: Spring Boot Actuatot heap dump #152

Open
mobbast opened this issue Dec 18, 2024 · 1 comment
Open

[Issue]: Spring Boot Actuatot heap dump #152

mobbast opened this issue Dec 18, 2024 · 1 comment

Comments

@mobbast
Copy link

mobbast commented Dec 18, 2024

Describe the Issue

Using the call below is it possible to get a Spring Boot Actuatot heap dump.

A heap dump is a snapshot of JVM memory, which could expose environment variables and HTTP requests.

Vulnerable URL: https://hyperwallet-prod.yoox.com:443/actuator/heapdump
Curl Command: curl -X 'GET' -d '' -H 'Host: hyperwallet-prod.yoox.com:443' -H 'User-Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2228.0 Safari/537.36' 'https://hyperwallet-prod.yoox.com:443/actuator/heapdump'

The urgency is not only due to the very critical nature of the vulnerability when accessing a dump of the JVM memory (which, as said, would contain sensitive information), but also to two main reasons urging us to make patching as faster as possible:

externally exposed application presence of particularly sensitive information, since the application handles transactions

These are the two main reasons that make it necessary to mitigate the vulnerability as quickly as possible, or to release a patch.”

Environment

Live/Production

Version

No response

Expected Behavior

Disable access to /actuator/heapdump for the URL identified.

Actual Behavior

No response

Steps to Reproduce

No response

Pre-conditions

No response

Relevant log output

No response

@jmlezcano
Copy link

jmlezcano commented Dec 19, 2024

Hi @mobbast,

Thanks for reaching out. I hope you are doing well!

Usually there are certains endpoints in applications that should have their access secured so that external access to these endpoints is not possible. The actuator heap dump endpoint is enabled by default so that users of the connector can access it to retrieve the information belonging to that endpoint, and shouldn't be exposed to external access due to the reasons you mentioned.

Is there a specific reason why this endpoint access has not being restricted in your application? If you have restrictions in place for certain endpoints, could this endpoint have been missed (and others)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants