{"id":216,"date":"2024-11-27T10:05:26","date_gmt":"2024-11-27T10:05:26","guid":{"rendered":"https:\/\/serisec.com\/index.php\/2024\/11\/27\/new-bluetooth-vulnerability-leak-your-passcode-to-hackers-while-pairing\/"},"modified":"2024-11-27T10:05:26","modified_gmt":"2024-11-27T10:05:26","slug":"new-bluetooth-vulnerability-leak-your-passcode-to-hackers-while-pairing","status":"publish","type":"post","link":"https:\/\/serisec.com\/index.php\/2024\/11\/27\/new-bluetooth-vulnerability-leak-your-passcode-to-hackers-while-pairing\/","title":{"rendered":"New Bluetooth Vulnerability Leak Your Passcode to Hackers While Pairing"},"content":{"rendered":"<p>    New Bluetooth Vulnerability Leak Your Passcode to Hackers While Pairing<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n    <!-- no image --><br \/>\n \t<BR><br \/>\n<BR><\/BR><\/p>\n<div>\n<p>A recently identified vulnerability in Bluetooth technology, identified as <a href=\"https:\/\/www.cve.org\/CVERecord?id=CVE-2021-37577\">CVE-2020-26558<\/a>, poses a significant security risk to devices supporting various Bluetooth Core Specifications. <\/p>\n<p>This vulnerability, known as \u201cImpersonation in the Passkey Entry Protocol,\u201d affects devices using the Passkey Entry association model in BR\/EDR Secure Simple Pairing, Secure Connections Pairing, and LE Secure Connections Pairing.<\/p>\n<h2 class=\"wp-block-heading\" id=\"h-vulnerability-details\"><strong>Vulnerability Details<\/strong><\/h2>\n<p>The flaw is present in Bluetooth Core Specifications ranging from version 2.1 through 5.4 for <a href=\"https:\/\/www.bluetooth.com\/learn-about-bluetooth\/tech-overview\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">BR\/EDR<\/a> to version 4.2 through 5.4 for LE Secure Connections. <\/p>\n<p>It allows a man-in-the-middle (<a href=\"https:\/\/cybersecuritynews.com\/wi-fi-mitm-attack\/\" target=\"_blank\" rel=\"noreferrer noopener\">MITM<\/a>) attacker to exploit the pairing process by responding to an initiating device with a public key whose X coordinate matches that of the peer device. <\/p>\n<p>By using crafted responses, the attacker can determine the passkey used during the pairing session, leading to an authenticated pairing procedure with both the initiating and responding devices.<\/p>\n<p>According to the Bluetooth <a href=\"https:\/\/www.bluetooth.com\/learn-about-bluetooth\/key-attributes\/bluetooth-security\/passkey-impersonation\/\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">report<\/a>, For this attack to be successful, the attacker must be within wireless range of two vulnerable Bluetooth devices that are initiating pairing or bonding. The attack specifically targets scenarios where a BR\/EDR or LE IO Capabilities exchange results in the selection of the Passkey pairing procedure.<\/p>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(135deg,rgb(238,238,238) 100%,rgb(169,184,195) 100%)\"><strong>Analyse Any Suspicious Links Using ANY.RUN\u2019s New Safe Browsing Tool:\u00a0<a href=\"https:\/\/app.any.run\/?utm_source=csn&amp;utm_medium=article&amp;utm_campaign=telegram_api&amp;utm_content=registration&amp;utm_term=031024\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Try for Free<\/a><\/strong><\/p>\n<h2 class=\"wp-block-heading\" id=\"h-recommendations-and-mitigations\"><strong>Recommendations and Mitigations<\/strong><\/h2>\n<p>To mitigate this risk, Bluetooth Core Specification 5.4 advises that devices should fail a pairing procedure if a peer\u2019s public key X coordinate matches that of the local device, except when a debug key is used. This check becomes mandatory in Bluetooth Core Specification 6.0.<\/p>\n<p>Experts recommend that manufacturers and developers adhere to these guidelines and update their implementations to comply with the latest specifications. Ensuring that devices reject public keys with matching X coordinates can prevent potential MITM attacks and enhance overall security.<\/p>\n<p>The Bluetooth Special Interest Group (SIG) emphasizes the importance of following updated security protocols to protect against vulnerabilities like CVE-2020-26558. Users are encouraged to update their devices regularly and stay informed about security patches released by device manufacturers.<\/p>\n<p>As Bluetooth technology continues evolving, maintaining robust security measures is crucial for safeguarding personal data and secure wireless communications.<\/p>\n<p class=\"has-text-align-center has-background\" style=\"background:linear-gradient(135deg,rgb(238,238,238) 100%,rgb(169,184,195) 100%)\"><strong>Free Webinar on How to Protect Small Businesses Against Advanced Cyberthreats<\/strong>\u00a0-&gt;\u00a0<strong><a href=\"https:\/\/my.demio.com\/ref\/eUcOj8lOn9xpgJb3?utm_source=cyber_security_news&amp;utm_medium=social&amp;utm_campaign=Q4-sponsored-webinars&amp;utm_content=ECMSIwebinar\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">Free Registration<\/a><\/strong><\/p>\n<p>The post <a rel=\"nofollow\" href=\"https:\/\/cybersecuritynews.com\/new-bluetooth-vulnerability-leak-your-passcode\/\">New Bluetooth Vulnerability Leak Your Passcode to Hackers While Pairing<\/a> appeared first on <a rel=\"nofollow\" href=\"https:\/\/cybersecuritynews.com\/\">Cyber Security News<\/a>.<\/p>\n<\/div>\n<p> \t<BR><br \/>\n <BR><\/BR><br \/>\n    Balaji N<br \/>\n \t<BR><br \/>\n<BR><\/BR><br \/>\n<a href=\"https:\/\/cybersecuritynews.com\/new-bluetooth-vulnerability-leak-your-passcode\/\">Go to cyber-security-news<\/a><br \/>\n \t<BR><br \/>\n <BR><\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"<p>New Bluetooth Vulnerability Leak Your Passcode to Hackers While Pairing A recently identified vulnerability in Bluetooth technology, identified as CVE-2020-26558, poses a significant security risk to devices supporting various Bluetooth Core Specifications. This vulnerability, known as \u201cImpersonation in the Passkey Entry Protocol,\u201d affects devices using the Passkey Entry association model in BR\/EDR Secure Simple Pairing, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[63,131],"tags":[130],"class_list":["post-216","post","type-post","status-publish","format-standard","hentry","category-cyber-security-news","category-vulnerability","tag-cyber-security-news"],"_links":{"self":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/216"}],"collection":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/comments?post=216"}],"version-history":[{"count":0,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/posts\/216\/revisions"}],"wp:attachment":[{"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/media?parent=216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/categories?post=216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/serisec.com\/index.php\/wp-json\/wp\/v2\/tags?post=216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}