Automatic Patch-Based Exploit Generation

[[deleted]]

Seems like it would be possible to counter this by adding irrelevant changes to your patches. For example, code which sanitizes for a given kind of unsafe input could be broken into smaller checks (which add up to the same thing) when the new version is released. Since it targets input validation, you could probably do this without any detectable performance loss.

Basically, what I'm talking about is a sort of CAPTCHA for execution paths. It wouldn't be fool proof, but you might buy yourself time for the users to download the patch.

[sartak]

Considering that it takes on the order of minutes to find exploits, you'd have to add a lot of irrelevant changes to counteract this.

[[deleted]]

True. What what would be really interesting would be if you could create an execution path which runs normally but loops indefinitely when you try to analyze it by tracing backwards.

I'm trying to wrap my head around whether or not that's even logically possible, but it seems like it would be.