CVE-2021-44518Public exploit

Lock takeover via cleartext BLE pairing code

Published Dec 2, 2021 · Updated Aug 4, 2024

Cleartext pairing-code transmission in the eGeeTouch Android travel-padlock app allows physically proximate attackers to control the lock over BLE. The companion app writes an authentication command containing the secret pairing code in cleartext to BLE attribute 0xfff8, exposing the credential to traffic capture. Exploitation requires the same companion app, capture of nearby BLE traffic, and physical access to press the lock's power button; the attacker can then change the pairing password and lock out the owner.

CVSS severity6.8
Medium
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Cleartext pairing-code transmission in the eGeeTouch Android travel-padlock app allows physically proximate attackers to control the lock over BLE. The companion app writes an authentication command containing the secret pairing code in cleartext to BLE attribute 0xfff8, exposing the credential to traffic capture. Exploitation requires the same companion app, capture of nearby BLE traffic, and physical access to press the lock's power button; the attacker can then change the pairing password and lock out the owner.

The record

CVE
CVE-2021-44518
Published
Dec 2, 2021
Updated
Aug 4, 2024
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-319, T1040
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 2, 2021CVE publishedPublication date reported by the CVE source.
  2. 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?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

2.9NIST NVDAV:A/AC:M/Au:N/C:P/I:N/A:N
6.8NIST NVDCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-319Cleartext Transmission of Sensitive Information
T1040Network Sniffing

Public exploit references

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