US government wants devs to stop using C and C++
CISA and the FBI urge developers to shift from memory-unsafe languages like C and C++ to memory-safe options by January 1, 2026, citing significant security risks and resistance to change.
Read original articleThe US Cybersecurity and Infrastructure Security Agency (CISA) and the FBI are urging software developers to move away from using "memory-unsafe" programming languages like C and C++. They emphasize that these languages pose significant risks to national security, economic stability, and public safety due to vulnerabilities such as buffer overflows. A report highlighted that over half of the analyzed critical open-source projects contain code in memory-unsafe languages, which account for 70% of security vulnerabilities. CISA recommends transitioning to memory-safe languages like Rust, Java, and Python, which offer built-in protections against common memory-related errors. However, the transition is complicated by the extensive time and resources required to convert existing codebases, as well as potential performance issues associated with newer languages. CISA has set a deadline for companies to develop roadmaps for this transition by January 1, 2026, arguing that the long-term benefits outweigh the initial costs. Despite these recommendations, many developers and companies are resistant to change, prioritizing speed and existing expertise in C and C++. The article suggests that while a shift to memory-safe languages is a good idea, it is unlikely to happen quickly, with significant resistance expected in the near term.
- CISA and FBI are advocating for a shift from C and C++ to memory-safe languages.
- Memory safety vulnerabilities account for 70% of security issues in software.
- Transitioning to new languages is resource-intensive and may affect performance.
- Companies must create transition roadmaps by January 1, 2026.
- Resistance to change is prevalent among developers and organizations.
Related
Investing in Rust
Investing in Rust programming language can enhance cybersecurity by preventing memory-related vulnerabilities. Challenges in adoption include integration issues and skill set mismatches, suggesting U.S. policy interventions for promotion.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety through bounds checking, smart pointers, and a dual strategy for teams.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety while acknowledging challenges and recommending a dual strategy for enhancement and migration.
The empire of C++ strikes back with Safe C++ blueprint
The Safe C++ Extensions proposal aims to enhance memory safety in C++, responding to demands for secure coding. It introduces compile-time checks and seeks broader industry participation for implementation.
The US government wants developers to stop using C and C++
CISA and the FBI urge developers to abandon memory-unsafe languages like C and C++ due to security risks, recommending a shift to memory-safe languages by January 1, 2026, despite challenges.
Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk (01.11.2024)
https://www.gao.gov/products/imtec-91-70br
Pursuant to a congressional request, GAO obtained information on the Department of Defense's (DOD) implementation of legislation which mandated using the Ada programming language for all software development, where cost-effective.
This misses the point. The point is to start moving in that direction, not instantaneously.
Literally anyone can call themselves a Software Engineer, which one the one hand is great because it's accessible, but also a curse in terms of making it a respected profession.
Related
Investing in Rust
Investing in Rust programming language can enhance cybersecurity by preventing memory-related vulnerabilities. Challenges in adoption include integration issues and skill set mismatches, suggesting U.S. policy interventions for promotion.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety through bounds checking, smart pointers, and a dual strategy for teams.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety while acknowledging challenges and recommending a dual strategy for enhancement and migration.
The empire of C++ strikes back with Safe C++ blueprint
The Safe C++ Extensions proposal aims to enhance memory safety in C++, responding to demands for secure coding. It introduces compile-time checks and seeks broader industry participation for implementation.
The US government wants developers to stop using C and C++
CISA and the FBI urge developers to abandon memory-unsafe languages like C and C++ due to security risks, recommending a shift to memory-safe languages by January 1, 2026, despite challenges.