One Article Review
| Source |  GoogleSec |
|---|---|
| Identifiant | 8611839 |
| Date de publication | 2024-11-15 12:42:24 (vue: 2024-11-15 18:07:46) |
| Titre | Retrofitting Spatial Safety to hundreds of millions of lines of C++ |
| Texte | Posted by Alex Rebert and Max Shavrick, Security Foundations, and Kinuko Yasada, Core DeveloperAttackers regularly exploit spatial memory safety vulnerabilities, which occur when code accesses a memory allocation outside of its intended bounds, to compromise systems and sensitive data. These vulnerabilities represent a major security risk to users. Based on an analysis of in-the-wild exploits tracked by Google\'s Project Zero, spatial safety vulnerabilities represent 40% of in-the-wild memory safety exploits over the past decade: Breakdown of memory safety CVEs exploited in the wild by vulnerability classGoogle is taking a comprehensive approach to memory safety. A key element of our strategy focuses on Safe Coding and using memory-safe languages in new code. This leads to an exponential decline in memory safety vulnerabilities and quickly improves the overall security posture of a codebase, as demonstrated by our post about Android\'s journey to memory safety.However, this transition will take multiple years as we adapt our development practices and infrastructure. Ensuring the safety of our billions of users therefore requires us to go further: we\'re also retrofitting secure-by-design principles to our existing C++ codebase wherever possible.To that end, we\'re working towards bringing spatial memory safety into as many of our C++ codebases as possible, including Chrome and the monolithic codebase powering our services.We\'ve begun by enabling hardened libc++, which adds bounds checking to standard C++ data structures, eliminating a significant class of spatial safety bugs. While C++ will not become fully memory-s |
| Notes | ★★★ |
| Envoyé | Oui |
| Condensat | acknowledgementswe based bridging we while 000 2022 ability about access accesses accidentally across actively adapt added adding address addressing adds advanced after ago aim alex all allocated allocation allowed allowing already also analysis and android another any applications approach are attempts automated available average avoid back bake baking: bar baseline become been before begun behavior benefits between beyond billions board boardbuilding both bounds bringing broader buffers bugs building but c++ carefully carruth case cases catch caught chandler changes check checked checking checks chrome class classgoogle close closely code codebase codebases coding collaborating comes commitment common community compiler components comprehensive compromise computing conducted contributed contributors core correctness correctness: corruption corruptions crashes create creating critical crucial current cves data debuggability debuggable debugging: decade decade:breakdown decline dedication default demonstrated demonstrating deploying deployment design designed despite detail developerattackers developers development diagnose difficult discussed disrupted disrupting drive due during duygu easier easily ecosystemhardened effective effectiveness efficient effort efforts element eliminate eliminating emilia empty enable enabled enablement enabling encourage end enhance enhancing ensures ensuring entire environments errors evaluations even eventual every example exception exercise existing expanding experience explains explicitly exploit exploitation exploited exploits exploits: exponential extensive fault feedback first fix fixed fixing fleet flip focused focuses foundation foundations from fully further further: future gap given giving gmail google gradual gradually guided had handful happened hardened hardening has have having heavy helpful how however hundreds identified identify identifying immediate impact impactin implement improved improvements improves improving including incorporate indicating individual infrastructure instance instances intended internal interoperability interoperate introduces investment isler isn issues iterators its java jeff journey just kasper key kinuko languages languages while leading leads led let libc++ libraries library libstdc++ like lines llvm low lower lurking made major making manifested many maps matthew max memory migrate migrating millions minimal minimize mirrors mode modern monitor monitored monolithic months more most moving multi multiple necessary new norm not notable noting now number occur one only open opted optimization optimizations organizations other otherwise out outage:testing: outside over overall overhead past paths percent performance perspective piece positive possible post posted posture potentially powering practical practice practices pre prevent prevented preventing previously primary principles process production productionenabling products profile programming project promptly provides puzzle python quality quantifiable quickly raise raising rate rather read rebert recently recognizing red reduce reduced reducing reduction redundant region regressions regularly reliability reliable remain remains represent require required requires requiring resources resulted retrofitting reviewed riley risk role rolled rollout rollout: runtime rust safe safer safety safetyone saving scale search secure security seen segfaults segmentation sensitive server services set several share shavrick showcases shrinks side significant similar similarly simple simplifies since small software source spatial spatially stage standard starting stays std::optional std::vector step stoep strategies strategy strongly structures structures: substantial successful such surfaced surprisingly switch systems take taking targeted team techniques testing tests than thank then therefore these third those thwarting time towards tracked transform transition translation uncovered underscores undetected uninitialized universally unnecessary unpredictable unsafe u |
| Tags | Vulnerability Threat Mobile |
| Stories | |
| 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.