Physical RFID credential cloning
Published Dec 4, 2023 · Updated Aug 2, 2024
Weak encryption in RFID tags in Yale Keyless Lock v1.0 allows attackers to create a cloned tag via physical proximity to the original. The lock uses MIFARE Classic cards without anti-cloning rolling codes, allowing an attacker close to or in direct physical contact with an unprotected credential to read its data and duplicate it. The cloned credential grants the same lock access as the original holder; it does not add permissions, and Yale reports no known unauthorized property access.
Summary
What happened
Weak encryption in RFID tags in Yale Keyless Lock v1.0 allows attackers to create a cloned tag via physical proximity to the original. The lock uses MIFARE Classic cards without anti-cloning rolling codes, allowing an attacker close to or in direct physical contact with an unprotected credential to read its data and duplicate it. The cloned credential grants the same lock access as the original holder; it does not add permissions, and Yale reports no known unauthorized property access.
The record
- CVE
- CVE-2023-26943
- Published
- Dec 4, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-326, T1078
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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.
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