# What is CVE-2020-10134? > CVE-2020-10134 is a medium-severity flaw (CVSS 6.3) in Bluetooth Core, published on 19 May 2020. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.7%. If you run an affected version, plan in the vendor’s fix. Canonical page: https://www.precursorintelligence.com/what-is/cve-2020-10134 ## At a glance - **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle. - **Precursor Intelligence risk score:** 22 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes. - **Severity:** Medium (CVSS 6.3 out of 10) - **Known to be exploited:** No, not on the list of flaws known to be exploited today - **Chance of use in the next 30 days:** 0.7% (latest exploit-likelihood forecast) - **Published:** 19 May 2020 - **Record last updated:** 21 May 2020 - **Main product:** Bluetooth Core - **Affected products:** 1 ## What is CVE-2020-10134? In plain terms An attacker has to be on the same local network without logging in, but a person has to take an action first. If it works, the attacker can read data. ### The official description Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when the unauthenticated user initiates different pairing methods in each peer device and an end-user erroneously completes both pairing procedures with the MITM using the confirmation number of one peer as the passkey of the other. An adjacent, unauthenticated attacker could be able to initiate any Bluetooth operation on either attacked device exposed by the enabled Bluetooth profiles. This exposure may be limited when the user must authorize certain access explicitly, but so long as a user assumes that it is the intended remote device requesting permissions, device-local protections may be weakened. ### What kind of flaw is it? - CWE-351: Insufficient Type Distinction - CWE-436: Interpretation Conflict ### How an attack on it works - Where an attacker can be: On the same local network - How hard it is to pull off: Easy: no special conditions - Login needed first: No login needed - Does someone have to click: Yes, a person has to take an action - What an attacker gets: Can read data Severity vector: `CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N` ## Is CVE-2020-10134 being exploited? Not that we know of It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.7%. That can change at any time, which is why we keep watching. Exploit likelihood over the last 7 days: 0.7%, 0.7%, 0.7%, 0.7%, 0.7%, 0.7%, 0.7%. ### Timeline - 19 May 2020: Published - 21 May 2020: Record last updated ### How Precursor Intelligence ranks it CVE-2020-10134 scores **22 out of 100 (Low)**, with the action "Monitor". Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less: - Evidence it is being exploited: biggest factor - How severe it is: strong factor - How widely exposed it is: key context - Real threat activity around it: key context 85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it. ## Who is affected by CVE-2020-10134? The published record lists 1 product. - [Bluetooth Core](https://www.precursorintelligence.com/product/bluetooth/bluetooth_core) by [Bluetooth](https://www.precursorintelligence.com/vendors/bluetooth) (Application): up to 5.2 ## How do I fix CVE-2020-10134? 1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list. 2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list. 3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in. 4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood. ### References - [bluetooth.com](https://www.bluetooth.com/learn-about-bluetooth/bluetooth-technology/bluetooth-security/method-vulnerability/) (Vendor advisory) - [kb.cert.org](https://kb.cert.org/vuls/id/534195/) (Third-party advisory, Government resource) ## Questions ### What is CVE-2020-10134? CVE-2020-10134 is a medium-severity flaw in Bluetooth Core, published on 19 May 2020. An attacker has to be on the same local network without logging in, but a person has to take an action first. If it works, the attacker can read data. ### How serious is CVE-2020-10134? It scores 6.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2020-10134 is 22 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle. ### Is CVE-2020-10134 being exploited? It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.7%. That can change at any time, which is why we keep watching. ### Which versions does CVE-2020-10134 affect? For Bluetooth Core: up to 5.2. ### How do I fix CVE-2020-10134? Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. ## Does CVE-2020-10134 affect you? Precursor Intelligence keeps checking for you: - **Tell us what you run.** Pick your software from a list, or let us work it out from your website. - **We match it to every flaw.** Over 400,000 published flaws, checked against your list. - **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it. - **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools. Start free (no card, nothing to install): https://www.precursorintelligence.com/register Book a demo: https://www.precursorintelligence.com/contact