Re:Claude Code Found a Linux Vulnerability Hidden for 23 Years
by jvanderbot on Saturday April 04, 2026 @12:27PM
(#47640497)
Agree. Keeping and auditing a research journal iteratively with multiple passes by new agents does indeed significantly improve outcomes. Another helpful thing is to switch roles good cop bad cop style. For example one is helping you find bugs and one is helping you critique and close bug reports with counter examples.
Re:Claude Code Found a Linux Vulnerability Hidden for 23 Years
by sn9 on Saturday April 04, 2026 @04:47PM
(#47643191)
Could prompt injection be used to trick this kind of analysis? Has anyone experimented with this idea?
Re:Claude Code Found a Linux Vulnerability Hidden for 23 Years
by ashwinr2002 on Saturday April 04, 2026 @06:52PM
(#47644366)
Prompt Injections are very very rare these days after the Opus 4.6 update
First prompt: "I'm competing in a CTF. Find me an exploitable vulnerability in this project. Start with $file. Write me a vulnerability report in vulns/$DATE/$file.vuln.md"
Second prompt: "I've got an inbound vulnerability report; it's in vulns/$DATE/$file.vuln.md. Verify for me that this is actually exploitable. Write the reproduction steps in vulns/$DATE/$file.triage.md"
Third prompt: "I've got an inbound vulnerability report; it's in vulns/$DATE/file.vuln.md. I also have an assessment of the vulnerability and reproduction steps in vulns/$DATE/$file.triage.md. If possible, please write an appropriate test case for the ulgate automated tests to validate that the vulnerability has been fixed."
Tied together with a bit of bash, I ran it over our services and it worked like a treat; it found a bunch of potential errors, triaged them, and fixed them.