# CVE-2021-44518: Information disclosure in n/a

> An attacker can capture unencrypted pairing codes via Bluetooth to take complete control of the smart lock.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gc5m-6c6c-jvx7

## What is CVE-2021-44518?

CVE-2021-44518 is a medium-severity vulnerability in n/a, published on 2 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2021-44518?

It affects 1 product.


Products: Digipas Egeetouch Manager.

## How do I fix CVE-2021-44518?

No fix has been published for CVE-2021-44518 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-44518 being exploited?

There is no known exploitation of CVE-2021-44518 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44518 and fix it if it is affected.

What it is: CVE-2021-44518 is a medium-severity vulnerability in n/a, published on 2 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-44518 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-44518/ (Markdown: https://insights.sbomify.com/CVE-2021-44518/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-44518
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-44518
- OSV: https://osv.dev/vulnerability/CVE-2021-44518

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-44518/
Summaries are generated and may contain mistakes; the official description above is the record.