Authentication bypass via failed-pairing state transition
Published Jun 27, 2025 · Updated Jul 2, 2025
Authentication bypass in Cypress PSoC4 BLE SDK 3.66 allows physically proximate attackers to enter encryption without pairing. The pairing and Link Layer state machine accepts LL_ENC_REQ after a crafted pairing_failed packet instead of returning to a safe state. BLE radio range and an active pairing exchange are required; the demonstrated result is unauthenticated entry into the encryption phase.
Summary
What happened
Authentication bypass in Cypress PSoC4 BLE SDK 3.66 allows physically proximate attackers to enter encryption without pairing. The pairing and Link Layer state machine accepts LL_ENC_REQ after a crafted pairing_failed packet instead of returning to a safe state. BLE radio range and an active pairing exchange are required; the demonstrated result is unauthenticated entry into the encryption phase.
The record
- CVE
- CVE-2025-44557
- Published
- Jun 27, 2025
- Updated
- Jul 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-303
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2025CVE publishedPublication date reported by the CVE source.
- Jul 2, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Cypress PSoC4 authentication-bypass proof of conceptproof of concept · 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