One Article Review
| Source |  GoogleSec |
|---|---|
| Identifiant | 8335705 |
| Date de publication | 2023-05-11 12:44:52 (vue: 2023-05-11 18:07:58) |
| Titre | Présentation d'une nouvelle façon de bourdonner pour les vulnérabilités EBPF Introducing a new way to buzz for eBPF vulnerabilities |
| Texte | Juan José López Jaimez, Security Researcher and Meador Inge, Security EngineerToday, we are announcing Buzzer, a new eBPF Fuzzing framework that aims to help hardening the Linux Kernel.What is eBPF and how does it verify safety?eBPF is a technology that allows developers and sysadmins to easily run programs in a privileged context, like an operating system kernel. Recently, its popularity has increased, with more products adopting it as, for example, a network filtering solution. At the same time, it has maintained its relevance in the security research community, since it provides a powerful attack surface into the operating system.While there are many solutions for fuzzing vulnerabilities in the Linux Kernel, they are not necessarily tailored to the unique features of eBPF. In particular, eBPF has many complex security rules that programs must follow to be considered valid and safe. These rules are enforced by a component of eBPF referred to as the "verifier". The correctness properties of the verifier implementation have proven difficult to understand by reading the source code alone. That\'s why our security team at Google decided to create a new fuzzer framework that aims to test the limits of the eBPF verifier through generating eBPF programs.The eBPF verifier\'s main goal is to make sure that a program satisfies a certain set of safety rules, for example: programs should not be able to write outside designated memory regions, certain arithmetic operations should be restricted on pointers, and so on. However, like all pieces of software, there can be holes in the logic of these checks. This could potentially cause unsafe behavior of an eBPF program and have security implications. |
| Envoyé | Oui |
| Condensat | now that 2023 2163 35k ability able about accomplish across actually added additionally adopting aims all allowed allows alone also announcing any arbitrary are arithmetic around attack automatically begin behavior branch bugs but buzz buzzer can cases cause certain checks code community complex complexity component considered context contributions contributors corner correctness could create cve decided demonstrates designated detect detected determine develop developers difficult distributed does each easily easy ebpf ebpfbuzzer efficient enforced engineertoday error errors example example: excited executed exploring feature features filtering first focusing follow forward found framework from fuzz fuzzer fuzzers fuzzing general generated generating generation github goal google hardening has have hearing help high holes how however ideas implement implementation implications includes increased inge instrumentation interesting introducing issue its jaimez josé juan kernel know leading let library like limits linux logic look looking lópez main maintained make makes making manner many meador memory minute more must necessarily network new not only open operating operations other outside overall overlooked particular paths per pieces plans pointers popularity potentially powerful privileged products program programs properties proven provides pruning purpose reading recently referred regions relevance repository research researcher researchers restricted rules run running runs runtime safe safer safety same satisfies security set should since software solution solutions some source strategies such sure surface sysadmins system tailor tailored takes task team technique technology test then these thinks through thus time together tries uncover understand unique unsafe use valid validation verifier verify vms volume vulnerabilities way what why will write writing your |
| Tags | |
| Stories | |
| Notes | ★★ |
| Move | 
|
L'article ne semble pas avoir été repris aprés sa publication.
L'article ne semble pas avoir été repris sur un précédent.