Credential disclosure via weak password encoding
Published Mar 28, 2025 · Updated Mar 28, 2025
Weak password encoding in Arteche saTECH BCU firmware 2.1.3 allows remote authenticated users to obtain stored credentials. The device stores passwords using encoding that lacks sufficient cryptographic strength, but Arteche has not disclosed the algorithm, storage locus, or recovery procedure. Access to the device system or website is required, and the documented consequence is credential disclosure.
Summary
What happened
Weak password encoding in Arteche saTECH BCU firmware 2.1.3 allows remote authenticated users to obtain stored credentials. The device stores passwords using encoding that lacks sufficient cryptographic strength, but Arteche has not disclosed the algorithm, storage locus, or recovery procedure. Access to the device system or website is required, and the documented consequence is credential disclosure.
The record
- CVE
- CVE-2025-2862
- Published
- Mar 28, 2025
- Updated
- Mar 28, 2025
- Vendor
- Arteche
- Product
- saTECH BCU
- Classifications
- CWE-261, T1555
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 28, 2025CVE publishedPublication date reported by the CVE source.
- Mar 28, 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=2.1.3
What conditions does exploitation require?
What is affected?
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.
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