CVE-2024-34463
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 · uneditedBPL Personal Weighing Scale PWS-01BT IND/09/18/599 devices send sensitive information in unencrypted BLE packets. (The packet data also lacks authentication and integrity protection.)
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 confidenceThe BPL Personal Weighing Scale PWS-01BT transmits sensitive user data (weight/health measurements) over Bluetooth Low Energy without encryption. Additionally, the BLE communication lacks authentication, allowing any nearby BLE device to potentially interact with the scale, and lacks integrity protection, meaning transmitted data could be modified without detection.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 the device modelInspect the physical device or packaging for the model number BPL Personal Weighing Scale PWS-01BT. Check product documentation or the BLE device name advertised over Bluetooth.Affected if The device is a BPL PWS-01BT scale
-
Verify BLE advertising is activeUse a BLE scanner app or tool (such as nRF Connect, BLE Explorer, or hcitool lescan) to detect if the scale is broadcasting BLE advertisements.Affected if The scale is actively broadcasting over BLE and is discoverable
-
Test for BLE authentication requirementAttempt to connect to the scale via BLE using a generic BLE client without completing any pairing or authentication handshake. Observe if a connection is established without credentials.Affected if Connection is established without requiring PIN, passkey, or other authentication
-
Sniff BLE traffic for encryptionUse a BLE sniffer (such as Wireshark with BLE adapter, BTVS, or similar) to capture packets transmitted by the scale during use. Examine the ATT/GATT data for plaintext weight measurements or health data.Affected if Sensitive data (weight, health metrics) is transmitted in plaintext without encryption layer
-
Check for data integrity protectionAnalyze captured BLE packets for the presence of message authentication codes, signatures, or sequence numbers that would detect tampering. Inject modified packets and verify if the device rejects or accepts them.Affected if Modified packets are accepted without detection or validation failure
A user is affected if they own a BPL PWS-01BT scale that transmits weight data over unencrypted, unauthenticated BLE and lacks integrity checks.
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 dataAvoid using this device for sensitive health data until a firmware update is available from BPL; contact the vendor for patched firmware or consider replacing with a device that supports encrypted BLE communications.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34463 — 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-2024-34463 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