Authentication bypass via shared SDKSocket secrets
Published Nov 1, 2025 · Updated Nov 1, 2025
Shared cryptographic keys in SDKSocket on BLU-IC2 and BLU-IC4 through 1.19.5 allow remote attackers to impersonate trusted peers. The TCP/5000 service uses the same secret across multiple devices instead of a unique per-device key, so possession of the shared key satisfies its cryptographic trust check. No authentication or user interaction is required, and successful access exposes device and downstream-system confidentiality, integrity, and availability.
Summary
What happened
Shared cryptographic keys in SDKSocket on BLU-IC2 and BLU-IC4 through 1.19.5 allow remote attackers to impersonate trusted peers. The TCP/5000 service uses the same secret across multiple devices instead of a unique per-device key, so possession of the shared key satisfies its cryptographic trust check. No authentication or user interaction is required, and successful access exposes device and downstream-system confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-12599
- Published
- Nov 1, 2025
- Updated
- Nov 1, 2025
- Vendor
- Azure Access Technology
- Product
- BLU-IC4
- Classifications
- CWE-321, CAPEC-191
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 1, 2025CVE publishedPublication date reported by the CVE source.
- Nov 1, 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 <=1.19.5
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