Vulnerability Report

Unauthorized Swagger UI Access and API Information Disclosure

SVID:202409200001 · CVSS 7.1 · High · Reported September 20, 2024
Report ID
SVID:202409200001
Severity
High
CVSS v4.0 Score
7.1 / 10
CVE ID
Pending assignment
Reported Date
September 20, 2024
Fixed Date
September 23, 2024
Reported By
Sigenergy Cybersecurity Red Team
Status
Fixed
Affected Component
SigenCloud API — Swagger UI / API Docs
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Summary

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

September 20, 2024

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.

September 23, 2024

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.

September 23, 2024

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

ComponentExposed PathsEnvironment
Swagger UI / API documentation /swagger-ui.html, /swagger-resources, /v2/api-docs, /v3/api-docs, /swagger.json, /swagger.yaml Production (EU)
Backend host: 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-docs and /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).

MetricValueMeaning
Attack Vector (AV)NetworkExploitable over the internet.
Attack Complexity (AC)LowThe documentation paths are directly accessible.
Attack Requirements (AT)NoneNo special preconditions.
Privileges Required (PR)NoneNo account is required.
User Interaction (UI)NoneNo victim interaction required.
Vulnerable System Confidentiality (VC)HighThe full API surface and sensitive business fields are disclosed.
Vulnerable System Integrity (VI)NoneNo direct integrity impact from documentation exposure.
Vulnerable System Availability (VA)NoneNo direct availability impact.
Subsequent System Confidentiality (SC)NoneNo impact beyond the vulnerable component.
Subsequent System Integrity (SI)NoneNo impact beyond the vulnerable component.
Subsequent System Availability (SA)NoneNo impact beyond the vulnerable component.

Technical Details / Proof of Concept

Step 1 — Access the interactive Swagger UI without authentication

# No authentication headers required GET /swagger-ui.html HTTP/2 Host: api-eu.sigenergy.com

Step 2 — Retrieve the machine-readable API documentation

# OpenAPI 3.x / 2.x specification endpoints GET /v3/api-docs HTTP/2 Host: api-eu.sigenergy.com GET /v2/api-docs HTTP/2 Host: api-eu.sigenergy.com GET /swagger.json HTTP/2 Host: api-eu.sigenergy.com

Step 3 — Enumerate the full API surface

HTTP/2 200 OK Content-Type: application/json {"swagger":"2.0","info":{"title":"SigenCloud API","version":"1.0"}, "paths":{"/device/sigen/device/list":{...},"/user/account/info":{...},"/order/list":{...}, ...}}
Attack vector assessment: high. The documentation reveals every endpoint, parameter and response field, giving an attacker a complete map for targeted probing — and the interactive UI can issue requests directly when backend validation is weak.

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

  1. Disable Swagger in production. Completely disable the Swagger UI and API documentation pages in the production environment.
  2. Gate non-production docs. Enable Swagger only in development/test environments, behind authentication and network isolation.
  3. Remove or feature-flag the documentation dependency so it cannot be re-enabled accidentally in a production build.
  4. Verify after every release that /swagger-ui.html, /swagger-resources, /v2/api-docs, /v3/api-docs, /swagger.json and /swagger.yaml return 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)
For questions about this report, or to report a related vulnerability, contact the Sigenergy Security Incident Response Team at csirt@sigenergy.cloud. See our Vulnerability Handling Process for how reports are managed.