{"id":"CVE-2020-11957","url":"https://www.cyber-defence.io/tools/cve/CVE-2020-11957","generatedAt":"2026-10-27T22:33:27.704Z","title":"A predictable or brute-forceable random number allows an attacker (in radio range) to perform a MITM attack during BLE pairing.","description":"The Bluetooth Low Energy implementation in Cypress PSoC Creator BLE 4.2 component versions before 3.64 generates a random number (Pairing Random) with significantly less entropy than the specified 128 bits during BLE pairing. This is the case for both authenticated and unauthenticated pairing with both LE Secure Connections as well as LE Legacy Pairing. A predictable or brute-forceable random number allows an attacker (in radio range) to perform a MITM attack during BLE pairing.","published":"2020-06-09T19:15:10.000Z","lastModified":"2026-06-17T02:51:08.000Z","status":"Modified","sourceIdentifier":"cve@mitre.org","cvss":{"version":"3.1","score":7.5,"severity":"HIGH","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"},"cwe":["CWE-331"],"affected":["cypress/psoc 4.2 ble"],"epss":{"score":0.00394,"percentile":0.33304,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.39%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[],"references":[{"url":"https://www.cypress.com/file/504466/download","tags":["Product","Vendor Advisory"],"source":"cve@mitre.org"},{"url":"https://www.cypress.com/file/504466/download","tags":["Product","Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-11957","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}