SVID:202409200001Pending assignmentSummary
An unauthorized Swagger UI and API documentation exposure on api-eu.sigenergy.com allows any anonymous user to enumerate the complete SigenCloud API surface — every endpoint path, request parameter, response schema and sensitive business field — without authentication.
Because the interactive Swagger UI also lets a visitor fill in parameters and send requests, the exposure further enables direct probing of backend endpoints, and when combined with weak backend authentication it can escalate to unauthorized operations, bulk queries and data tampering.
Handling Timeline
Vulnerability reported
The unauthorized Swagger UI and API documentation exposure was reported to the Sigenergy Security Incident Response Team by the Sigenergy Cybersecurity Red Team.
Fix deployed by Sigenergy Cloud
The Sigenergy Cloud department remediated the issue by disabling the Swagger UI and API documentation endpoints in the production environment.
Fix re-verified
The remediation was re-verified on September 23, 2024. The Swagger UI and API documentation paths no longer return content and are properly restricted in production.
Affected Products / Components
| Component | Exposed Paths | Environment |
|---|---|---|
| Swagger UI / API documentation | /swagger-ui.html, /swagger-resources, /v2/api-docs, /v3/api-docs, /swagger.json, /swagger.yaml | Production (EU) |
https://api-eu.sigenergy.com
Vulnerability Description
The SigenCloud API production host exposed its Swagger UI and machine-readable API documentation without any authentication or authorization control. An unauthenticated visitor could browse the interactive documentation and read every API endpoint path, request parameter, response structure and sensitive business field.
Root cause
- The Swagger UI page was not disabled during development or deployment to production.
- No access control (Authentication / Authorization) was applied to the documentation paths such as
/swagger-ui.html,/v2/api-docs,/v3/api-docsand/swagger.json.
Impact
- Information disclosure — an attacker can directly view all API endpoint paths, request parameters, response structures and sensitive business fields.
- Unauthorized operations — where backend interfaces lacked strict token/session validation, an attacker could fill in parameters and send requests directly from the Swagger page, enabling privilege escalation, bulk queries and data tampering.
CVSS v4.0 Scoring
The report assigns a CVSS v4.0 Base Score of 7.1 (High).
| Metric | Value | Meaning |
|---|---|---|
| Attack Vector (AV) | Network | Exploitable over the internet. |
| Attack Complexity (AC) | Low | The documentation paths are directly accessible. |
| Attack Requirements (AT) | None | No special preconditions. |
| Privileges Required (PR) | None | No account is required. |
| User Interaction (UI) | None | No victim interaction required. |
| Vulnerable System Confidentiality (VC) | High | The full API surface and sensitive business fields are disclosed. |
| Vulnerable System Integrity (VI) | None | No direct integrity impact from documentation exposure. |
| Vulnerable System Availability (VA) | None | No direct availability impact. |
| Subsequent System Confidentiality (SC) | None | No impact beyond the vulnerable component. |
| Subsequent System Integrity (SI) | None | No impact beyond the vulnerable component. |
| Subsequent System Availability (SA) | None | No impact beyond the vulnerable component. |
Technical Details / Proof of Concept
Step 1 — Access the interactive Swagger UI without authentication
Step 2 — Retrieve the machine-readable API documentation
Step 3 — Enumerate the full API surface
Impact
- Information disclosure — complete exposure of API endpoint paths, request parameters, response structures and sensitive business fields.
- Unauthorized operations — the interactive page can submit requests, enabling privilege escalation, bulk queries and data tampering on weakly protected endpoints.
- Attack-surface reconnaissance — the documentation accelerates targeted attacks by mapping the entire backend.
Remediation & Recommendations
- Disable Swagger in production. Completely disable the Swagger UI and API documentation pages in the production environment.
- Gate non-production docs. Enable Swagger only in development/test environments, behind authentication and network isolation.
- Remove or feature-flag the documentation dependency so it cannot be re-enabled accidentally in a production build.
- Verify after every release that
/swagger-ui.html,/swagger-resources,/v2/api-docs,/v3/api-docs,/swagger.jsonand/swagger.yamlreturn 403/404 in production.
References
- Affected host:
https://api-eu.sigenergy.com - Weakness:
CWE-200(Exposure of Sensitive Information to an Unauthorized Actor),CWE-306(Missing Authentication for Critical Function) - OWASP Top 10 2021 —
A05:2021(Security Misconfiguration)