Credential disclosure via plaintext firmware storage
Published Mar 11, 2025 · Updated Mar 11, 2025
Cleartext credential storage in Tinxy smart-device firmware allows physically proximate attackers to extract credentials from all versions. The firmware image stores device credentials as readable plaintext, so static inspection of the extracted binary reveals them without decryption. Exploitation requires physical possession and firmware extraction, and the documented consequence is credential disclosure rather than device modification or service interruption.
Summary
What happened
Cleartext credential storage in Tinxy smart-device firmware allows physically proximate attackers to extract credentials from all versions. The firmware image stores device credentials as readable plaintext, so static inspection of the extracted binary reveals them without decryption. Exploitation requires physical possession and firmware extraction, and the documented consequence is credential disclosure rather than device modification or service interruption.
The record
- CVE
- CVE-2025-2189
- Published
- Mar 11, 2025
- Updated
- Mar 11, 2025
- Vendor
- Mogify Infotech LLP
- Product
- Tinxy 1 Node 10A and 16A Smart Wi-Fi Switches
- Classifications
- CWE-312, CAPEC-37, T1552.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2025CVE publishedPublication date reported by the CVE source.
- Mar 11, 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=all versions
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