SVID:202409120001Pending assignmentSummary
The /actuator/heapdump endpoint of the SigenCloud API was exposed without authentication and returned a full Java Virtual Machine (JVM) heap dump to anyone who requested it. Visiting https://api.sigencloud.com/actuator/heapdump triggers an automatic download of a binary .hprof file.
A heap dump is a snapshot of the JVM memory at a point in time. When opened in a memory-analyzer tool (such as Eclipse Memory Analyzer), it can reveal in-memory credentials, database connection strings, API keys, session tokens, signing keys and cached personal data belonging to Sigenergy customers.
Handling Timeline
Detected by Sigenergy Cybersecurity
The exposed /actuator/heapdump endpoint was identified by the Sigenergy Cybersecurity team during internal security testing.
Fixed & verified
Sigenergy disabled the heap dump endpoint in production and restricted Actuator access. The fix has been verified.
Affected Products / Components
| Component | Endpoint / URL | Environment |
|---|---|---|
| SigenCloud API — Spring Boot Actuator | GET /actuator/heapdump | Production |
https://api.sigencloud.com
Vulnerability Description
Spring Boot Actuator exposes operational endpoints (health, metrics, env, heapdump, etc.) for monitoring and management. When these endpoints are reachable from the internet without authentication, an attacker can invoke them directly.
The /actuator/heapdump endpoint returns a heap dump of the application's JVM. It produces a file with the .hprof extension — a binary format that can be opened and examined in a memory-analyzer tool. When the endpoint is visited, the file is downloaded automatically.
Data that can typically be recovered from a heap dump includes:
- Database credentials — connection strings and passwords held in memory.
- API keys and tokens — third-party service keys and JWT signing secrets.
- Session data — active user session identifiers and authentication material.
- Cached personal data — customer names, contact details and account data.
Root Cause
- Exposed management endpoint. The Spring Boot Actuator endpoints were reachable on the public API host without authentication.
- Heap dump endpoint enabled in production.
/actuator/heapdumpwas enabled and publicly accessible, exposing the full JVM memory. - Missing access control. No network restriction or authentication gate protected the Actuator endpoints.
CVSS v4.0 Scoring
The report assigns a CVSS v4.0 Base Score of 9.2 (Critical).
| Metric | Value | Meaning |
|---|---|---|
| Attack Vector (AV) | Network | Exploitable over the internet. |
| Attack Complexity (AC) | Low | Only requires requesting the endpoint. |
| Attack Requirements (AT) | None | No special preconditions. |
| Privileges Required (PR) | None | No authentication required. |
| User Interaction (UI) | None | No victim interaction required. |
| Vulnerable System Confidentiality (VC) | High | Leaks the full JVM heap, including secrets and PII. |
| Vulnerable System Integrity (VI) | None | No data modification. |
| Vulnerable System Availability (VA) | None | No availability impact. |
| Subsequent System Confidentiality (SC) | High | Leaked credentials and tokens enable further compromise of connected systems. |
| Subsequent System Integrity (SI) | None | No integrity impact on subsequent systems. |
| Subsequent System Availability (SA) | None | No availability impact on subsequent systems. |
Technical Details / Proof of Concept
Step 1 — Request the heap dump endpoint
An unauthenticated HTTP request to the Actuator heap dump endpoint triggers an automatic download of the heap dump file:
Step 2 — The server returns the JVM heap dump
Step 3 — Examine the heap dump in a memory analyzer
Open the downloaded .hprof file in a memory-analyzer tool (e.g. Eclipse Memory Analyzer, VisualVM) and search for credentials, tokens and cached personal data.
Impact
A successful attack can expose sensitive information held in the application's memory:
- Credential disclosure — database passwords, API keys and signing secrets may be recovered from the heap.
- Account and service compromise — leaked credentials and tokens can be used to access backend services and customer accounts.
- Personal data disclosure — cached customer data (names, contact details) may be extracted.
- Compliance exposure — disclosure of personal data may trigger GDPR and other data-breach obligations.
Remediation & Recommendations
- Disable the heap dump endpoint in production. Set
management.endpoint.heapdump.enabled=false. - Restrict Actuator access. Keep Actuator endpoints on an internal management port and require authentication, or block them at the network edge.
- Rotate all credentials and secrets that may have been resident in memory (database passwords, API keys, signing keys).
- Audit exposure. Review access logs for requests to
/actuator/heapdumpto determine whether the endpoint was accessed by third parties.
Additional hardening (recommended)
- Disable Actuator in production unless explicitly required for monitoring.
- Use an allow-list of permitted Actuator endpoints and a dedicated internal management port.
- Run regular external exposure scans for common misconfigurations such as exposed Actuator endpoints.
References
- Affected endpoint:
https://api.sigencloud.com/actuator/heapdump - Weakness:
CWE-200(Exposure of Sensitive Information to an Unauthorized Actor) - OWASP Top 10 2021 —
A05:2021(Security Misconfiguration)