Latest / Ctrl AI Profit / Ep. 263 | OpenAI and Google's AI Found a Hole Under Your Business Website
Transcript
- 0:20SPEAKER_00: Security researchers using AI from OpenAI and Google found two serious holes in the software that quietly runs a huge share of the world's websites, and there's a good chance yours is one of them.
- 0:33SPEAKER_01: That's the news in one sentence.
- 0:35SPEAKER_01: The fix came out October 21st, and government cyber agencies in the US, the UK, and Europe told website owners to update right away.
- 0:46SPEAKER_00: Okay, slow down for me.
- 0:48SPEAKER_00: What software?
- 0:49SPEAKER_00: I didn't install anything.
- 0:51SPEAKER_01: That's the point.
- 0:52SPEAKER_01: You probably didn't.
- 0:54SPEAKER_01: It's called PHP, and it's the one new word for this episode.
- 0:58SPEAKER_01: So let me define it.
- 0:59SPEAKER_01: Go ahead.
- 1:00SPEAKER_01: Plain English.
- 1:01SPEAKER_01: PHP is the engine under the hood of a website.
- 1:05SPEAKER_01: When somebody visits your site, PHP is the part on the server that builds the page and sends it to them.
- 1:11SPEAKER_01: WordPress runs on it.
- 1:12SPEAKER_01: So do Drupal and Joomla, and a lot of online stores.
- 1:16SPEAKER_00: So if my website is built on WordPress, it's sitting on top of PHP, whether I knew it or not.
- 1:22SPEAKER_01: Exactly.
- 1:24SPEAKER_01: You see WordPress.
- 1:26SPEAKER_01: Underneath it, PHP is doing the work.
- 1:29SPEAKER_01: And the holes are in that underneath part.
- 1:32SPEAKER_01: How bad are we talking?
- 1:34SPEAKER_01: The PHP team rated both flaws critical.
- 1:38SPEAKER_01: In plain terms, a stranger could send your website a specially built request and take control of the server.
- 1:43SPEAKER_01: No password, no login.
- 1:45SPEAKER_01: And a related trick could pull passwords and keys out of the server's memory.
- 1:49SPEAKER_01: Without logging in.
- 1:51SPEAKER_00: That's the part that gets me.
- 1:53SPEAKER_01: Same.
- 1:53SPEAKER_01: And the security firm Wiz says every version of PHP released in the last decade has at least one of these problems.
- 2:00SPEAKER_00: A decade.
- 2:01SPEAKER_00: So why are we only hearing about it now?
- 2:05SPEAKER_01: That's where the AI comes in.
- 2:07SPEAKER_01: The code was hard to break.
- 2:09SPEAKER_01: Turning these flaws into a working attack took a chain of steps that Wiz says was right at the edge of what human researchers could pull off.
- 2:17SPEAKER_01: And the AI made it easy.
- 2:19SPEAKER_01: Easier.
- 2:20SPEAKER_01: Two groups found it.
- 2:22SPEAKER_01: A firm called Caliph found one using OpenAI's model through an OpenAI program called Patch the Planet.
- 2:28SPEAKER_01: Wiz found both on its own and says Google's Gemini 4 Argonne made what it called an invaluable contribution.
- 2:35SPEAKER_00: So this is the AI story.
- 2:37SPEAKER_00: Not a chatbot writing emails, a computer finding a hole that people walked past for 10 years.
- 2:44SPEAKER_01: Right.
- 2:45SPEAKER_01: Wiz put it this way.
- 2:47SPEAKER_01: One researcher with these tools did in a week what used to take a world-class team months.
- 2:52SPEAKER_01: Which is great when the good guys have it.
- 2:54SPEAKER_01: And that's the catch.
- 2:56SPEAKER_01: OpenAI said it out loud in its own post.
- 2:59SPEAKER_01: The same abilities that help defenders find holes can help attackers build the break-in tools faster.
- 3:05SPEAKER_01: So the clock matters here.
- 3:08SPEAKER_01: It does.
- 3:09SPEAKER_01: The plan was a quiet, coordinated fix, but according to the BBC, details leaked on social media the day before, so the fix went out in a rush, and Cloudflare's technology chief said they were already seeing early attacks.
- 3:21SPEAKER_01: I read that some big websites just shut off.
- 3:26SPEAKER_01: They did.
- 3:27SPEAKER_01: The Finnish government took public web services down.
- 3:30SPEAKER_01: The Dutch Cyber Agency took its own site offline.
- 3:33SPEAKER_01: The UK Cybercenter and the NSA both said, if you can't update, consider taking the site down until you can.
- 3:41SPEAKER_00: Okay, that's the scary part.
- 3:42SPEAKER_00: Now let's make it useful.
- 3:44SPEAKER_00: I'm an owner.
- 3:44SPEAKER_00: I've got a website some guy built five years ago.
- 3:47SPEAKER_00: What do I actually do?
- 3:49SPEAKER_01: Step one.
- 3:50SPEAKER_01: Find out what your site runs on.
- 3:52SPEAKER_01: If you ever log into something called WordPress to change your hours or post a photo, you're on PHP.
- 3:59SPEAKER_01: And if I don't know?
- 4:01SPEAKER_01: Then step one is a text to whoever built it or hosts it.
- 4:05SPEAKER_01: That's the shop move for this whole episode.
- 4:08SPEAKER_01: What does the text say?
- 4:10SPEAKER_01: Give me words I can copy.
- 4:13SPEAKER_01: Something like, is our website on PHP and has it been updated to the October 21st security release?
- 4:19SPEAKER_01: That's it.
- 4:20SPEAKER_01: Whoever runs your site will know exactly what you mean.
- 4:23SPEAKER_00: And what's the right answer?
- 4:25SPEAKER_00: So I know if they're just telling me what I want to hear.
- 4:29SPEAKER_01: The fixed versions are 8.5.2, 8.4.27, 8.3.36, and 8.2.35.
- 4:39SPEAKER_01: Those numbers or newer?
- 4:41SPEAKER_01: I'm not going to remember that.
- 4:43SPEAKER_01: You don't have to.
- 4:44SPEAKER_01: They're in the show notes.
- 4:46SPEAKER_01: Just paste them in the text.
- 4:48SPEAKER_00: Can I check it myself in WordPress?
- 4:52SPEAKER_01: Usually yes.
- 4:53SPEAKER_01: In the WordPress dashboard, go to Tools, then Cite Health, then the Info tab.
- 5:00SPEAKER_01: Open the server section, and it shows your PHP version.
- 5:04SPEAKER_00: Here's what I'd have gotten wrong.
- 5:06SPEAKER_00: I'd have clicked update all on my WordPress plugins and called it done.
- 5:11SPEAKER_01: And that's the trap.
- 5:12SPEAKER_01: Updating WordPress doesn't fix this.
- 5:14SPEAKER_01: The hole is underneath WordPress on the server.
- 5:18SPEAKER_01: Your host or your web person has to update PHP itself.
- 5:22SPEAKER_00: What if my version number is older, like 8.1?
- 5:27SPEAKER_01: Then you need a real conversation.
- 5:29SPEAKER_01: The PHP project stops sending updates for 8.1 and older.
- 5:33SPEAKER_01: Some hosting companies patch old versions on their own, so the number alone won't tell you.
- 5:38SPEAKER_01: Ask your host directly whether you're protected.
- 5:42SPEAKER_00: And if I'm on one of those website builders where I never see a server at all.
- 5:48SPEAKER_01: Then the server is their job, not yours.
- 5:51SPEAKER_01: But it's still fair to look for their notice or ask support.
- 5:55SPEAKER_00: 30 seconds.
- 5:56SPEAKER_00: One more thing I'd add.
- 5:57SPEAKER_00: If your site has a login, like for customers or staff, and your web person finds it was exposed, change those passwords after the update.
- 6:07SPEAKER_01: Good call.
- 6:08SPEAKER_01: Wiz specifically said passwords and keys could be pulled from memory, so update first, then change passwords.
- 6:16SPEAKER_00: Last question.
- 6:21SPEAKER_01: Expect more.
- 6:22SPEAKER_01: OpenAI said these bugs are among several serious ones it's already working to fix, and it expects findings like this to increase sharply in the coming months.
- 6:30SPEAKER_00: So the real takeaway isn't just this one update.
- 6:33SPEAKER_00: It's knowing that somebody is keeping the server under my website up to date without me having to read the news.
- 6:40SPEAKER_01: Right.
- 6:41SPEAKER_01: If your hosting plan says it handles updates for you, ask whether that includes PHP.
- 6:47SPEAKER_01: If nobody's responsible, settle that before the next one, not during it.
- 6:52SPEAKER_00: So the shop rule is simple.
- 6:55SPEAKER_00: You don't need to understand the code.
- 6:57SPEAKER_00: You need to know who holds the keys to your website, and you need one text from them that says updated.
- 7:04SPEAKER_01: And if you don't know who holds the keys, that's the real problem this week showed you.
- 7:08SPEAKER_00: Thanks for hanging out with us.
- 7:10SPEAKER_00: If this saved you a confusing afternoon, send it to the owner you know who has a WordPress site and no idea who's running it.
- 7:16SPEAKER_00: We'll see you next time on Control AI Profit.
- 7:20SPEAKER_01: See you next time.