Inside Google's "promising and pragmatic" approach to fixing software development's memory safety problem

Google's recent security post highlights the overwhelming dangers of memory safety bugs, revealing that they account for 70% of severe vulnerabilities found in memory unsafe codebases, emphasizing the critical need for transitioning towards memory safe languages.

In its analysis, Google revealed that 75% of CVEs used in zero-day exploits relate to memory safety vulnerabilities, indicating an urgent need to address these weaknesses in software development quickly and efficiently.

The tech giant recognizes that transitioning away from memory unsafe languages like C and C++ is not immediate, as critical legacy systems require considerable ongoing support, but commits to ensuring robust practices within existing frameworks.

Google's pragmatic approach to memory safety aims for balanced integration of memory safe languages while maintaining robust operations in existing memory unsafe code, acknowledging both short-term challenges and long-term goals.

Read at ITPro