Vulnerability Report

Unauthorized MQTT Broker Access (Port 1883/8883)

SVID:202412060001 · CVSS 9.3 · Critical · Reported December 6, 2024
Report ID
SVID:202412060001
Severity
Critical
CVSS v4.0 Score
9.3 / 10
CVE ID
Pending assignment
Reported Date
December 6, 2024
Fixed Date
December 10, 2024
Reported By
Sigenergy Cybersecurity Red Team
Status
Fixed
Affected Component
SigenCloud MQTT Broker — Port 1883 / 8883
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Summary

An unauthorized access vulnerability in the SigenCloud MQTT broker at mqtt**-eu.sigencloud.com allows any anonymous client to connect, subscribe to and publish messages on ports 1883 (plaintext) and 8883 (TLS) — without any username, password or client-certificate authentication.

Because MQTT carries device telemetry and control traffic, an attacker who connects anonymously can read every device message, inject forged commands, and disrupt the messaging infrastructure — a full confidentiality, integrity and availability compromise with no prior credentials.

Handling Timeline

December 6, 2024

Vulnerability reported

The unauthorized MQTT broker access was reported to the Sigenergy Security Incident Response Team by the Sigenergy Cybersecurity Red Team.

December 10, 2024

Fix deployed by Sigenergy Cloud

The Sigenergy Cloud department remediated the issue by enforcing mandatory MQTT authentication and access control on both ports, and disabling anonymous connections.

December 10, 2024

Fix re-verified

The remediation was re-verified on December 10, 2024. Anonymous connections are now rejected and the broker requires valid credentials on ports 1883 and 8883.

Affected Products / Components

ComponentHostPortsEnvironment
SigenCloud MQTT Broker mqtt**-eu.sigencloud.com 1883 (MQTT/TCP), 8883 (MQTT/TLS) Production (EU)
Broker host: mqtt**-eu.sigencloud.com:1883 and mqtt**-eu.sigencloud.com:8883

Vulnerability Description

The production MQTT broker accepted anonymous connections — no username/password and no client certificate were required on either the plaintext port 1883 or the TLS port 8883. An unauthenticated client could connect, subscribe to all topics (including the # wildcard) and publish arbitrary messages to any topic.

Root cause

  • The MQTT broker was configured with anonymous access enabled (no authentication backend enforced).
  • No Access Control List (ACL) restricted which topics a client could subscribe to or publish on.
  • The TLS port 8883 provided transport encryption only — encryption was mistaken for authentication, so the broker remained open to anonymous clients.

Impact

  • Information disclosure — an attacker can subscribe to # and read all device telemetry, status, and configuration messages.
  • Device control / message injection — an attacker can publish forged control commands, causing unauthorized device operations.
  • Denial of service — an attacker can flood the broker with messages, disrupting the messaging infrastructure.

CVSS v4.0 Scoring

The report assigns a CVSS v4.0 Base Score of 9.3 (Critical).

MetricValueMeaning
Attack Vector (AV)NetworkExploitable over the internet.
Attack Complexity (AC)LowThe broker accepts anonymous connections directly.
Attack Requirements (AT)NoneNo special preconditions.
Privileges Required (PR)NoneNo account or credentials are required.
User Interaction (UI)NoneNo victim interaction required.
Vulnerable System Confidentiality (VC)HighAll device messages can be read via anonymous subscription.
Vulnerable System Integrity (VI)HighForged control messages can be published to devices.
Vulnerable System Availability (VA)HighThe messaging infrastructure can be flooded and disrupted.
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 — Connect anonymously to the broker (no credentials)

# Plaintext port 1883 — no username/password required mosquitto_sub -h mqtt**-eu.sigencloud.com -p 1883 -t '#' -v # TLS port 8883 — also accepts anonymous connections mosquitto_sub -h mqtt**-eu.sigencloud.com -p 8883 -t '#' -v

Step 2 — Subscribe to every topic and observe device traffic

# Wildcard subscription leaks all telemetry and status device/eu/120240***0006/telemetry {"power":4123,"soc":82,"temp":31} device/eu/120240***0006/status {"state":"grid-tied","alarm":0} station/eu/120240***0002/energy {"today":18.4,"total":9321}

Step 3 — Publish forged messages without authentication

# An attacker can publish to control topics directly mosquitto_pub -h mqtt**-eu.sigencloud.com -p 1883 \ -t "device/eu/120240***0006/command" -m '{"action":"set_power","value":0}'
Attack vector assessment: critical. Anonymous subscribe + publish on a device-control channel enables full interception and forgery of operational traffic with no credentials.

Impact

  • Information disclosure — complete exposure of device telemetry, status and energy data via anonymous wildcard subscription.
  • Device control / message injection — forged control commands can be published, enabling unauthorized device operations.
  • Denial of service — the broker can be flooded, disrupting message delivery across the platform.
  • Mass exploitation — no credentials are needed, so the vulnerability is trivially exploitable at scale.

Remediation & Recommendations

  1. Disable anonymous access. Reject all connections that do not present valid credentials.
  2. Enforce authentication on both ports 1883 and 8883 (username/password or, preferably, mutual TLS client certificates).
  3. Apply Access Control Lists (ACL) so each client can only subscribe to and publish on its own authorized topics.
  4. Rotate credentials for all devices and services that were exposed during the vulnerable window.
  5. Monitor for abnormal connections and alert on wildcard (#/+) subscriptions and high-rate publishing.

References

  • Affected host: mqtt**-eu.sigencloud.com:1883, mqtt**-eu.sigencloud.com:8883
  • Weakness: CWE-306 (Missing Authentication for Critical Function)
  • OWASP Top 10 2021 — A07:2021 (Identification and Authentication Failures)
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.