Home › Hard problems › Security

Security

Memory-unsafe code everywhere

Solo: strongOne person can run a real test of this in about 8 weeks.

a buffer with 8 slotssecretnext stepa write runs past the end, and C does not stop itmost serious C and C++ security bugsare memory errors like thisC and C++:billionsof linesrewrite it all in Rust by hand?unaffordable
C and C++ let a write run past the end of a buffer, which causes most serious security bugs, and there is far too much of that code to rewrite by hand.

Why it is still open

Most serious security bugs in C and C++ come from memory errors. Rewriting billions of lines in Rust by hand is unaffordable.

An experiment one person can run in 8 weeks

Have an LLM translate 50 small C programs to safe Rust and measure how many compile, pass tests and avoid "unsafe" blocks.

Verdict: Solo: strong

Pass-or-fail results and a public push for memory safety.

The solo test behind the verdict

  1. Can it be measured? There is a number that shows you did better, such as an error rate, a catch rate or a cost per answer.
  2. Is it cheap to try? It runs on a laptop, free open models and open data, or under about ₹50,000 of rented GPU time.
  3. Is there a public yardstick? A benchmark or dataset others use, so your result can be compared and believed.
  4. Would a small win get noticed? A lab, a funder or a customer would care about a 10% improvement, not only a full solution.

Four yeses means Solo: strong. Two or three means Solo: possible. Fewer means Follow, don't build.

NextMalicious packages in software supply chains

All 79 hard problems · Working on this, or know of a result we missed? basant@cleandataengineering.ai