MQTT credential disclosure via exposed backend script
Published Feb 6, 2022 · Updated Aug 3, 2024
Information disclosure in Servisnet Tessa 0.0.2 allows remote attackers to obtain MQTT credentials via a /js/app.js request. The publicly served backend app.js file embeds a default Authorization header and connectionMQTT values, including the MQTT host, port, client ID, username, and password. No authentication or user interaction is required; the exposed credentials grant access to the separate MQTT service.
Summary
What happened
Information disclosure in Servisnet Tessa 0.0.2 allows remote attackers to obtain MQTT credentials via a /js/app.js request. The publicly served backend app.js file embeds a default Authorization header and connectionMQTT values, including the MQTT host, port, client ID, username, and password. No authentication or user interaction is required; the exposed credentials grant access to the separate MQTT service.
The record
- CVE
- CVE-2022-22833
- Published
- Feb 6, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Servisnet Tessa MQTT Credentials Dump Unauthenticated Metasploit modulefunctional · demonstrated
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