In our first post in this series, we discussed the need for proactively addressing memory safety issues. Tools and guidance are demonstrably not preventing this class of vulnerabilities; memory safety issues have represented almost the same proportion of vulnerabilities assigned a CVE for over a decade. We feel that using memory-safe languages will mitigate this in ways that tools and training have not been able to.
Print
Share
Comment
Cite
Upload
Translate
APA
() » We need a safer systems programming language. Retrieved from https://www.truth.cx/2019/07/18/we-need-a-safer-systems-programming-language/.
MLA" » We need a safer systems programming language." - , https://www.truth.cx/2019/07/18/we-need-a-safer-systems-programming-language/
HARVARD » We need a safer systems programming language., viewed ,
VANCOUVER - » We need a safer systems programming language. [Internet]. [Accessed ]. Available from: https://www.truth.cx/2019/07/18/we-need-a-safer-systems-programming-language/
CHICAGO" » We need a safer systems programming language." - Accessed . https://www.truth.cx/2019/07/18/we-need-a-safer-systems-programming-language/
IEEE" » We need a safer systems programming language." [Online]. Available: https://www.truth.cx/2019/07/18/we-need-a-safer-systems-programming-language/. [Accessed: ]