hn.today

AI is forcing us to pay off 40 years of technical debt

spectrum.ieee.org923 points562 comments
Screenshot of AI is forcing us to pay off 40 years of technical debt

The PHP2Shell vulnerability shows how AI is changing the cybersecurity risk posed by decades-old software. A memory-allocation bug in PHP, reported in 2024, was initially treated as a routine crash rather than a serious threat. In an audit sponsored by OpenAI, researchers at cybersecurity firm Calif used AI tools to turn it into a way to run arbitrary code on vulnerable servers, potentially exposing sensitive data or enabling malware. The affected software underpins many websites, including systems such as WordPress and Drupal. Researchers disclosed the issue before attackers exploited it, and the PHP Foundation released a patch after four engineers spent two months preparing one.

The episode illustrates a widening imbalance: AI can help specialists find and exploit complex bugs faster, while safely fixing them requires ensuring every attack path is closed without breaking existing software. AI does not replace cybersecurity expertise, but it lets leading researchers work more efficiently and may help less-specialized people reach that level. The discussion points to two responses: fund maintainers of widely used open-source projects and give defenders access to advanced security models; and develop formal verification tools that can check AI-generated patches. One researcher is optimistic that this work can become increasingly automated, while another warns that substantial investment may only follow a major public-facing breach. The practical advice is to install security updates promptly. PHP2Shell, the researchers warn, is likely an early example of AI exposing vulnerabilities accumulated across decades of software development.

Read on spectrum.ieee.org562 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

Upcoming change for eMudhra CA certificates included in the Chrome Root Store

Upcoming change for eMudhra CA certificates included in the Chrome Root Store

Chrome will stop trusting new TLS certificates issued under eMudhra’s emSign Root CA G1 in Chrome 153 and later if their earliest timestamp is after November 16, 2026. Google cited eMudhra’s failure to adequately explain weak key generation that exposed eight subordinate CA private keys; older certificates and explicitly trusted certificates are unaffected. (groups.google.com)

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.