CVE-2017-1000250: Infoleak

Published Sep 7, 2017
·
Updated

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.

Other sources

Information disclosure vulnerability due to out-of-bounds heap read in servicesearchattrreq function when processing of incoming requests in the SDP server was found. Unauthenticated attacker can exploit this vulnerability to read potentially sensitive data from heap of the bluetoothd process.

Vulnerable code:

... } else { / continuation State exists -> get from cache / sdpbuft pCache = sdpgetcachedrsp(cstate); if (pCache) { uint16t sent = MIN(max, pCache->datasize - cstate->cStateValue.maxBytesSent); pResponse = pCache->data; memcpy(buf->data, pResponse + cstate->cStateValue.maxBytesSent, sent); buf->datasize += sent; cstate->cStateValue.maxBytesSent += sent; if (cstate->cStateValue.maxBytesSent == pCache->datasize) cstatesize = sdpsetcstatepdu(buf, NULL); else cstatesize = sdpsetcstatepdu(buf, cstate); } else { status = SDPINVALIDCSTATE; SDPDBG("Non-null continuation state, but null cache buffer"); } } ...

When a long response is returned to a specific search attribute request, a continuation state is returned to allow reception of additional fragments, via additional requests that contain the last continuation state sent. However, the incoming “cstate” that requests additional fragments isn’t validated properly, and thus an out-of-bounds read of the response buffer (pResponse) can be achieved, leading to information disclosure of the heap.

Red Hat

Affected Software

1 affected component
bluez bluez<=5.46

Event History

Sep 7, 2017
Data Sourced
via Red Hat·01:18 PM
DescriptionSeverityAffected Software
Sep 12, 2017
CVE Published
via MITRE·05:00 PM
Data Sourced
via MITRE·05:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-1000250?

CVE-2017-1000250 is classified as a medium severity vulnerability due to its potential for information disclosure.

2

How do I fix CVE-2017-1000250?

To fix CVE-2017-1000250, upgrade to BlueZ version 5.47 or later, which includes the necessary security patches.

3

What kind of data can be exposed due to CVE-2017-1000250?

CVE-2017-1000250 allows remote attackers to access sensitive information from the process memory of Bluetooth services.

4

Who is affected by CVE-2017-1000250?

CVE-2017-1000250 affects users running BlueZ versions 5.46 and earlier.

5

Is there a workaround for CVE-2017-1000250?

There are no known workarounds for CVE-2017-1000250; the best mitigation is to upgrade to the latest version of BlueZ.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203