ID CVE-2017-1000250
Summary 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.
References
Vulnerable Configurations
  • cpe:2.3:a:bluez:bluez:5.41:*:*:*:*:*:*:*
    cpe:2.3:a:bluez:bluez:5.41:*:*:*:*:*:*:*
  • cpe:2.3:a:bluez:bluez:5.42:*:*:*:*:*:*:*
    cpe:2.3:a:bluez:bluez:5.42:*:*:*:*:*:*:*
  • cpe:2.3:a:bluez:bluez:5.46:*:*:*:*:*:*:*
    cpe:2.3:a:bluez:bluez:5.46:*:*:*:*:*:*:*
CVSS
Base: 3.3 (as of 17-02-2018 - 02:29)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
ADJACENT_NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
cvss-vector via4 AV:A/AC:L/Au:N/C:P/I:N/A:N
redhat via4
advisories
bugzilla
id 1489446
title CVE-2017-1000250 bluez: Out-of-bounds heap read in service_search_attr_req function
oval
OR
  • AND
    • OR
      • comment Red Hat Enterprise Linux 6 Client is installed
        oval oval:com.redhat.rhba:tst:20111656001
      • comment Red Hat Enterprise Linux 6 Server is installed
        oval oval:com.redhat.rhba:tst:20111656002
      • comment Red Hat Enterprise Linux 6 Workstation is installed
        oval oval:com.redhat.rhba:tst:20111656003
      • comment Red Hat Enterprise Linux 6 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20111656004
    • OR
      • AND
        • comment bluez is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685013
        • comment bluez is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685014
      • AND
        • comment bluez-alsa is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685017
        • comment bluez-alsa is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685018
      • AND
        • comment bluez-compat is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685011
        • comment bluez-compat is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685012
      • AND
        • comment bluez-cups is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685015
        • comment bluez-cups is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685016
      • AND
        • comment bluez-gstreamer is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685009
        • comment bluez-gstreamer is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685010
      • AND
        • comment bluez-libs is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685007
        • comment bluez-libs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685008
      • AND
        • comment bluez-libs-devel is earlier than 0:4.66-2.el6_9
          oval oval:com.redhat.rhsa:tst:20172685005
        • comment bluez-libs-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685006
  • AND
    • OR
      • comment Red Hat Enterprise Linux 7 Client is installed
        oval oval:com.redhat.rhba:tst:20150364001
      • comment Red Hat Enterprise Linux 7 Server is installed
        oval oval:com.redhat.rhba:tst:20150364002
      • comment Red Hat Enterprise Linux 7 Workstation is installed
        oval oval:com.redhat.rhba:tst:20150364003
      • comment Red Hat Enterprise Linux 7 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20150364004
    • OR
      • AND
        • comment bluez is earlier than 0:5.44-4.el7_4
          oval oval:com.redhat.rhsa:tst:20172685028
        • comment bluez is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685014
      • AND
        • comment bluez-cups is earlier than 0:5.44-4.el7_4
          oval oval:com.redhat.rhsa:tst:20172685027
        • comment bluez-cups is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685016
      • AND
        • comment bluez-hid2hci is earlier than 0:5.44-4.el7_4
          oval oval:com.redhat.rhsa:tst:20172685025
        • comment bluez-hid2hci is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685026
      • AND
        • comment bluez-libs is earlier than 0:5.44-4.el7_4
          oval oval:com.redhat.rhsa:tst:20172685023
        • comment bluez-libs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685008
      • AND
        • comment bluez-libs-devel is earlier than 0:5.44-4.el7_4
          oval oval:com.redhat.rhsa:tst:20172685024
        • comment bluez-libs-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20172685006
rhsa
id RHSA-2017:2685
released 2017-09-12
severity Moderate
title RHSA-2017:2685: bluez security update (Moderate)
rpms
  • bluez-0:4.66-2.el6_9
  • bluez-alsa-0:4.66-2.el6_9
  • bluez-compat-0:4.66-2.el6_9
  • bluez-cups-0:4.66-2.el6_9
  • bluez-gstreamer-0:4.66-2.el6_9
  • bluez-libs-0:4.66-2.el6_9
  • bluez-libs-devel-0:4.66-2.el6_9
  • bluez-0:5.44-4.el7_4
  • bluez-cups-0:5.44-4.el7_4
  • bluez-hid2hci-0:5.44-4.el7_4
  • bluez-libs-0:5.44-4.el7_4
  • bluez-libs-devel-0:5.44-4.el7_4
refmap via4
bid 100814
cert-vn VU#240311
confirm
debian DSA-3972
misc https://www.armis.com/blueborne
Last major update 17-02-2018 - 02:29
Published 12-09-2017 - 17:29
Back to Top