Skip to main content

KrØØk: Serious vulnerability affected encryption of billion+ Wi‑Fi devices

KrØØk: Serious vulnerability affected encryption of billion+ Wi‑Fi devices

  https://www.tekcrispy.com/wp-content/uploads/2020/03/vulnerabilidad-kr%C3%98%C3%98k-wifi.jpg

ESET Research has published its latest white paper, KrØØk – CVE-2019-15126: Serious vulnerability deep inside your Wi-Fi encryption. This blogpost summarizes that white paper, authored by researchers Miloš Čermák, Robert Lipovský and Štefan Svorenčík. For updated information regarding patches by individual vendors, readers can also refer to our dedicated webpage.
ESET researchers discovered a previously unknown vulnerability in Wi-Fi chips and named it KrØØk. This serious flaw, assigned CVE-2019-15126, causes vulnerable devices to use an all-zero encryption key to encrypt part of the user’s communication. In a successful attack, this allows an adversary to decrypt some wireless network packets transmitted by a vulnerable device.
KrØØk affects devices with Wi-Fi chips by Broadcom and Cypress that haven’t yet been patched. These are the most common Wi-Fi chips used in contemporary Wi-Fi capable devices such as smartphones, tablets, laptops, and IoT gadgets.

Not only client devices but also Wi-Fi access points and routers with Broadcom chips were affected by the vulnerability, thus making many environments with unaffected or already patched client devices vulnerable anyway.
Our tests confirmed that prior to patching, some client devices by Amazon (Echo, Kindle), Apple (iPhone, iPad, MacBook), Google (Nexus), Samsung (Galaxy), Raspberry (Pi 3), Xiaomi (RedMi), as well as some access points by Asus and Huawei, were vulnerable to KrØØk. This totaled to over a billion Wi-Fi-capable devices and access points, at a conservative estimate. Further, many other vendors whose products we did not test also use the affected chipsets in their devices.
The vulnerability affects both WPA2-Personal and WPA2-Enterprise protocols, with AES-CCMP encryption.
KrØØk is related to KRACK (Key Reinstallation Attacks), discovered in 2017 by Mathy Vanhoef, but also fundamentally different. In the beginning of our research, we found KrØØk to be one of the possible causes behind the “reinstallation” of an all-zero encryption key, observed in tests for KRACK attacks. This followed our previous findings that Amazon Echo was vulnerable to KRACK.
We responsibly disclosed the vulnerability to chip manufacturers Broadcom and Cypress, who subsequently released updates during an extended disclosure period. We also worked with the Industry Consortium for Advancement of Security on the Internet (ICASI) to ensure that all potentially affected parties – including affected device manufacturers using the vulnerable chips, as well as any other possibly affected chip manufacturers – were aware of KrØØk.
According to our information, patches for devices by major manufacturers have been released by now. To protect yourself, as a user, make sure you have applied the latest available updates to your Wi-Fi-capable devices, including phones, tablets, laptops, IoT devices, and Wi-Fi access points and routers. As a device manufacturer, please inquire about patches for the KrØØk vulnerability directly with your chip manufacturer.
These findings were presented publicly for the first time at the RSA Conference 2020.
Special thanks to our colleagues Juraj Bartko and Martin Kaluznik, who greatly contributed to this research. We’d also like to commend Amazon, Broadcom, and Cypress for their good cooperation on dealing with the reported issues and ICASI for their assistance in informing as many of the impacted vendors as possible.

Comments

Popular posts from this blog

Loading Android

アンドロイドQのための準備ができてあなたのアプリを入手! コンシューマーリリースが間もなくリリースされる予定で、すべての Android 開発者ができるだけ早く現在のアプリを更新して、できるだけ早く共同アプリを更新することが最優先事項です。 それを行う方法は次のとおりです。 Android Qにアプリをインストールする:Android QベータデバイスまたはエミュレータにGoogle Playから現在のアプリをインストールし、その後、t est。アプリは、完全な機能を備えた、実行と見栄えが良く、適切に実行する必要があります。すべての Android Q の動作が適切に変更されます。プライバシーの変更、ジェスチャー ナビゲーション、Bionic ライブラリの動的リンカー パスへの変更、および oth ers による影響を確認します。 新しい場所のアクセス許可、バックグラウンドアクティビティの制限、データと識別子の変更など、Android Q プライバシー機能を使用してテストします。開始するには、プライバシー チェックリストを参照し、動作の変更ドキュメントを確認して、テストする領域の詳細を確認してください。 制限付き非 SDK インターフェイスの使用をテストし、代わりにパブリック SDK または NDK に移動します。詳しくはこちらをご覧ください。 アプリでライブラリと SDK をテストする: Android Q で期待どおりに動作し、privac y、パフォーマンス、UX、データ処理、およびアクセス許可のベスト プラクティスに従っていることを確認します。問題が見つかった場合は、最新バージョンの SDK に更新するか、SDK 開発者に問い合わしてください。ここで SDK 互換性の問題を報告することもできます。 互換性のあるアプリを更新して公開する: テストが終了し、更新を行った場合は、互換性のあるアプリをすぐに公開することをお勧めします。これにより、Androidベータ版のユーザーは今アプリをテストすることができ、彼らはAndroi d Qに更新するユーザーにスムーズな移行を提供するのに役立ちます。 これらの変更をサポートすることはお客様にとっても投資であり、お客様のap ps への影響を最小限に抑え、最終リリースに向けてお客様の入力に応答する...