Physical entry via clonable unencrypted NFC tags
Published Jan 11, 2024 · Updated Jun 20, 2025
Missing encryption in NFC tags in Flient Smart Door Lock 1.0 allows physically proximate attackers to clone a tag and unlock a door. The lock accepts replayed data captured from an authorized NFC tag because the credential lacks encryption or a challenge-response check. Brief proximity to an original tag is sufficient to copy its data; presenting the clone grants physical access through the protected perimeter.
Summary
What happened
Missing encryption in NFC tags in Flient Smart Door Lock 1.0 allows physically proximate attackers to clone a tag and unlock a door. The lock accepts replayed data captured from an authorized NFC tag because the credential lacks encryption or a challenge-response check. Brief proximity to an original tag is sufficient to copy its data; presenting the clone grants physical access through the protected perimeter.
The record
- CVE
- CVE-2023-50129
- Published
- Jan 11, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-311
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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
- NFC Copying via Flipper Zerofunctional · 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