What is CVE-2020-10134?A medium-severity flaw in Bluetooth Core, explained.
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.
Published 19 May 2020. Record last updated 21 May 2020. We keep this page's data up to date.
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.
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-351Insufficient Type Distinction
- CWE-436Interpretation Conflict
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan 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.
Timeline
- Published
- Record last updated
CVE-2020-10134 scores 22. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2020-10134 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2020-10134? One product.
The published record lists 1 product from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
Bluetooth Core
by Bluetooth
Affected versionsup to 5.2
How do I fix CVE-2020-10134? Four steps.
- Check whether you run itCompare 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.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack 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.
Does CVE-2020-10134 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Pairing in Bluetooth® Core v5.2 and earlier may permit an unauthenticated attacker to acquire credentials with two pairing devices via adjacent access when t...
- Matched to
- Bluetooth Core on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
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.
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.
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.
For Bluetooth Core: up to 5.2.
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.