Enterprise LinuxOperating system · Redhat
CVE-2021-0129
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper access control in BlueZ may allow an authenticated user to potentially enable information disclosure via adjacent access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceBlueZ (Linux Bluetooth protocol stack) contains an improper access control vulnerability that allows an authenticated user to potentially disclose information via adjacent (Bluetooth range) access. The vulnerability stems from insufficient authorization checks in the Bluetooth stack that permit a user with adjacent access to access data they should not have permissions for.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Enterprise LinuxOperating system
= 7.0= 8.0
Debian LinuxOperating system
= 9.0< 5.57CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed BlueZ versionRun 'dpkg -l | grep bluez' on Debian/Ubuntu, 'rpm -qa | grep bluez' on RHEL/CentOS, or check the bluez package version through your package managerAffected if BlueZ version is below 5.57 (for upstream BlueZ) or on RHEL 7.0/8.0 or Debian 9.0 without patches
-
Verify Bluetooth service statusRun 'systemctl status bluetooth' or 'service bluetooth status' to check if the Bluetooth service is activeAffected if Bluetooth service is running and enabled, exposing the attack surface
-
Check for paired Bluetooth devicesRun 'bluetoothctl list' or 'hcitool devices' to enumerate paired Bluetooth devicesAffected if There are paired devices present, any of which could potentially exploit adjacent access
-
Inspect Bluetooth controller configurationRun 'hciconfig -a' to view Bluetooth adapter configuration and discoverable/connectable settingsAffected if Adapter is set to discoverable or connectable mode without proper restrictions
You are affected if BlueZ version is below 5.57 (or on the specific RHEL/Debian versions listed) AND Bluetooth is enabled with paired devices in range.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.57
Update BlueZ to the latest patched version that addresses this access control vulnerability. If patching is not immediately possible, limit Bluetooth exposure by restricting device pairing and ensuring only trusted devices can connect.
Fix this in Enterprise Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0129 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-0129 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data