CVE-2024-46539
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 · uneditedInsecure permissions in the Bluetooth Low Energy (BLE) component of Fire-Boltt Artillery Smart Watch NJ-R6E-10.3 allow attackers to cause a Denial of Service (DoS).
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 Fire-Boltt Artillery Smart Watch NJ-R6E-10.3 contains insecure permission configurations in its BLE stack that allow unauthorized attackers to trigger a Denial of Service condition, likely through malformed BLE connection requests or permission bypass enabling disruptive operations.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:H
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.
-
Confirm device modelIdentify the exact smart watch model number. Check device packaging, settings menu, or system information for the model identifier NJ-R6E-10.3 or confirm it is a Fire-Boltt Artillery Smart Watch.Affected if The device model matches Fire-Boltt Artillery Smart Watch NJ-R6E-10.3 exactly.
-
Verify BLE is enabledAccess the watch settings and check if Bluetooth Low Energy (BLE) is turned on. Look for Bluetooth or wireless connectivity settings on the device.Affected if BLE is currently enabled on the device.
-
Inspect BLE permission settingsNavigate to the watch Bluetooth settings or paired devices menu. Look for any permission, authorization, or connection settings related to BLE pairing, visibility, or connection requests.Affected if BLE permissions are set to allow unauthenticated connections or there are no visible authorization controls on BLE connections.
-
Check firmware versionIn the watch settings, look for a firmware or software version entry, typically under 'About Device', 'System', or 'Device Info' sections. Record the exact version string if present.Affected if The firmware version is available and differs from any vendor-provided patched version, or no version information is displayed.
You are likely affected if you own the Fire-Boltt Artillery Smart Watch NJ-R6E-10.3 and have BLE enabled, as the vulnerability resides in the BLE stack permission configuration of this specific device model.
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 dataApply any available firmware update from the vendor that addresses BLE permission controls; if no update exists, restrict BLE proximity or disable BLE when not in use.
- 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-2024-46539 — 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-46539 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