Login
You're viewing the functional.cafe public feed.
  • Nov 16, 2026, 11:56 PM

    @bagder How many of the not directly memory related were caused by correct memory management in C making the code paths that complex that the actual, non memory related bug slipped in, simply because the person writing the code lost track? How many would have been avoided if curl would have opted for more expressive, error detailing function signatures that are convenient in other programming languages, but inconvenient in plain C?

    💬 1🔄 0⭐ 0

Replies

  • 💬 1🔄 0⭐ 0
  • Nov 17, 2026, 2:15 AM

    @bagder You didn't list the 14 vulnerabilities you consider C issues, so I have to guess. Also only 63 of the 81 vulnerabilities are published yet, AFAIK.

    I've found 3805, 8925, 9080, 10536, 18924, 80229, 92388, 92392 and 107928 to be classified as C errors already.

    Your judgement on 11586 not being C seems implausibel to me: In other languages you wouldn't manipulate private date of objects, and the manipulation API of a restricted high-level buffer would check boundaries.

    💬 0🔄 0⭐ 0