Unauthorized door unlocking via replayed requests
Published Jun 23, 2020 · Updated Aug 4, 2024
Authentication bypass in Tinxy Door Lock firmware before 3.2 allows remote attackers to unlock a door by replaying an authorized request. The firmware accepts a previously valid Unlock request after the sender's door access has been revoked instead of requiring a fresh authorization decision. The attacker must have captured the request while authorized; replaying it later grants physical entry by unlocking the associated door.
Summary
What happened
Authentication bypass in Tinxy Door Lock firmware before 3.2 allows remote attackers to unlock a door by replaying an authorized request. The firmware accepts a previously valid Unlock request after the sender's door access has been revoked instead of requiring a fresh authorization decision. The attacker must have captured the request while authorized; replaying it later grants physical entry by unlocking the associated door.
The record
- CVE
- CVE-2020-9438
- Published
- Jun 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-294
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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