MQTT credential disclosure via insufficient password protection
Published May 14, 2024 · Updated Nov 3, 2025
Cleartext credential storage in Siemens SICAM OPUPI0 AMQP/MQTT before 5.30 allows attackers to retrieve MQTT client passwords. The device stores MQTT client passwords without sufficient protection; Siemens has not disclosed the exact storage locus or protection failure. Remote shell access or physical access is required, and successful retrieval exposes only the stored MQTT credentials.
Summary
What happened
Cleartext credential storage in Siemens SICAM OPUPI0 AMQP/MQTT before 5.30 allows attackers to retrieve MQTT client passwords. The device stores MQTT client passwords without sufficient protection; Siemens has not disclosed the exact storage locus or protection failure. Remote shell access or physical access is required, and successful retrieval exposes only the stored MQTT credentials.
The record
- CVE
- CVE-2024-31486
- Published
- May 14, 2024
- Updated
- Nov 3, 2025
- Vendor
- Siemens
- Product
- SICAM OPUPI0 AMQP/MQTT
- Classifications
- CWE-312, CAPEC-37, T1555
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <V5.30
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo