NVD / CVE Program· CNA mitre

CVE-2017-1000250: All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an information disclosure vulnerability which allows remote attac

Noroxi assessment

Priority: Monitor (action score 28/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 7.7% (FIRST EPSS); higher than 94.6% of all records.
Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: bluez (Alpine:v3.3) 5.36-r1; bluez (Alpine:v3.4) 5.40-r1; bluez (Alpine:v3.5) 5.42-r1.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to bluez (Alpine:v3.3) 5.36-r1; bluez (Alpine:v3.4) 5.40-r1; bluez (Alpine:v3.5) 5.42-r1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an information disclosure vulnerability which allows remote attackers to obtain sensitive information from the bluetoothd process memory. This vulnerability lies in the processing of SDP search attribute requests.

MediumCVSS 6.5 · v3.0—Proof of concept Fix available

Published: Sep 12, 2017
Updated: Jun 16, 2026
EPSS: 7.7% · 94th percentile
CWE: CWE-200

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 7.7%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
bluez	bluez	cpe:2.3:a:bluez:bluez

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

bluez bluezup to 5.46 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.3	bluez	before 5.36-r1	5.36-r1
Alpine:v3.4	bluez	before 5.40-r1	5.40-r1
Alpine:v3.5	bluez	before 5.42-r1	5.42-r1
Alpine:v3.6	bluez	before 5.44-r3	5.44-r3
Debian:12	bluez	before 5.46-1	5.46-1
Debian:7	bluez	before 4.99-2+deb7u1	4.99-2+deb7u1
Debian:8	bluez	before 5.23-2+deb8u1	5.23-2+deb8u1
Debian:9	bluez	before 5.43-2+deb9u1	5.43-2+deb9u1
Red Hat:enterprise_linux:6::client	bluez	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-alsa	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-compat	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-cups	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-debuginfo	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-gstreamer	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-libs	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:6::client	bluez-libs-devel	before 0:4.66-2.el6_9	0:4.66-2.el6_9
Red Hat:enterprise_linux:7::client	bluez	before 0:5.44-4.el7_4	0:5.44-4.el7_4
Red Hat:enterprise_linux:7::client	bluez-cups	before 0:5.44-4.el7_4	0:5.44-4.el7_4
Red Hat:enterprise_linux:7::client	bluez-debuginfo	before 0:5.44-4.el7_4	0:5.44-4.el7_4
Red Hat:enterprise_linux:7::client	bluez-hid2hci	before 0:5.44-4.el7_4	0:5.44-4.el7_4
Red Hat:enterprise_linux:7::client	bluez-libs	before 0:5.44-4.el7_4	0:5.44-4.el7_4
Red Hat:enterprise_linux:7::client	bluez-libs-devel	before 0:5.44-4.el7_4	0:5.44-4.el7_4
SUSE:Linux Enterprise Desktop 12 SP3	bluez	before 5.13-5.4.1	5.13-5.4.1
SUSE:Linux Enterprise Server for SAP Applications 12 SP1	bluez	before 5.13-3.10.1	5.13-3.10.1

Same product

bluez: all records

Other highest-scoring records for the same primary product.

CVE-2024-8805BlueZ HID over GATT Profile Improper Access Control Remote Code Execution Vulnerability
36Monitor
CVE-2022-0204A heap overflow vulnerability was found in bluez in versions prior to 5.63.
36Monitor
CVE-2021-43400An issue was discovered in gatt-database.c in BlueZ 5.61.
36Monitor

Published before and after this one in the same product

← EarlierCVE-2016-9917Dec 8, 2016 · In BlueZ 5.42, a buffer overflow was observed in "read_n" function in "tools/hcidump.c" source file.
31Monitor
← EarlierCVE-2016-7837Jun 9, 2017 · Buffer overflow in BlueZ 5.41 and earlier allows an attacker to execute arbitrary code via the parse_line function used in some userland uti
31Monitor
Later →CVE-2018-10910Jan 28, 2019 · A bug in Bluez may allow for the Bluetooth Discoverable state being set to on when no Bluetooth agent is registered with the system.
13Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
alpine:bluez	5.36-r1 · Alpine:v3.3	Package registry (OSV)
debian:bluez	5.46-1 · Debian:12	Package registry (OSV)
red hat:bluez	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-alsa	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-compat	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-cups	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-debuginfo	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-gstreamer	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-hid2hci	0:5.44-4.el7_4 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:bluez-libs	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
red hat:bluez-libs-devel	0:4.66-2.el6_9 · Red Hat:enterprise_linux:6::client	Package registry (OSV)
suse:bluez	5.13-5.4.1 · SUSE:Linux Enterprise Desktop 12 SP3	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:5	2017-11-12

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedSep 12, 2017
First PoCNov 12, 2017+60 d
TodayOct 27, 2026+3332 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-17-112 · Sep 12, 2017(BlueBorne Bluetooth Zafiyeti)

All national notices →

Technical details

Attack conditions

Someone on the same network segment can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Adjacent
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{
2  "permissions": ["tabs", "<all_urls>"],
3  "background": { "service_worker": "analytics.js" }
4}

Fixed

json

1{
2  "permissions": ["activeTab"],
3  "host_permissions": ["https://yildiz.example/*"]
4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

nvidia.custhelp.com/app/answers/detail/a_id/4561

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records