45
"No way to prevent this" say users of only language where this regularly happens - 07/01/2024 (xeiaso.net)
submitted 2 years ago by to c/programmer_humor@programming.dev
21 comments fedilink hide all child comments
 

A shitpost about languages that generate CVEs

you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (2 children)

... the only language where 90% of the world's memory safety vulnerabilities have occurred in the last 50 years

Yeah... That's a shit post alright.

I'm not a C developer myself, but that's just a low blow. Also, uncited ;).

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 9 points 2 years ago* (last edited 2 years ago) (1 child)

    This is an overstatement, definitely. C is one of the few (mainstream) languages where memory safety vulnerabilities are even possible. So if you batch C and C++ together, they probably cover more than 90% of all the memory unsafe cove written in last 50 years, which is a strong implication that they will contribute to 90% of memory vulnerabilities.

    All that said, memory vulnerabilities are about 65% of all high implact vulnerabilities on Chromium project^1 and about 70% of vulnerabilities at Microsoft ^2.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •