Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

The Low Down

The Low Down artwork

Fable Ban Fallout, Nightmare Eclipse's Microsoft Revenge, and the $40M iOS Exploit Kit

Jul 6, 202659 minAudioSeason 1, Episode 2
ShareXLinkedInFacebookWhatsAppEmail

Welcome to The Low Down, the best show on the internet for hackers The Low Down is presented by Maze. LinkedIn: https://www.linkedin.com/company/mazehq/ X: https://twitter.com/Maze_Security Follow Us! https://www.instagram.com/lowdown.pod This week we're broadcasting live from the PlanetScale office at the AI Engineering Conference in San Francisco, diving deep into the most pressing issues in cybersecurity right now. Today we're talking about: The Fable Ban & AI Export Controls Breaking down the unprecedented government intervention that pulled Fable from public access, the Free Fable movement, and what this means for AI security research going forward. We discuss the export control implications and why this sets a dangerous precedent. Mythos, Project Glasswing & The Future of Exploit Development Why Mythos and Fable aren't uniquely dangerous despite the government narrative, how AI is genuinely changing vulnerability research, and the philosophical questions around automated exploitation capabilities. Open Weight Models & The China Question Examining DeepSeek, Kimi, and other Chinese models that are rapidly catching up to frontier capabilities, plus Meta's internal restrictions on competitor model usage and what it reveals about the industry. Beats by Dre Bluetooth RCE Vulnerability A year-old vulnerability finally patched that gave attackers remote code execution on Bluetooth headphones, allowing microphone access, call initiation, and complete device control within proximity range. Nightmare Eclipse & The Rogue Planet Exploit The latest Windows Defender zero day from the controversial researcher, featuring a race condition that allows malware placement in System32. We discuss the painful disclosure saga, MSRC's reputation crisis, and what this means for bug bounty programs. The Bug Bounty Crisis Why researchers are revolting against major programs like MSRC and Apple, the broken social contract of responsible disclosure, and how AI is reshaping the economics of vulnerability research. Karuna & Darksword: The $40 Million Exploit Kit Discussing the leaked government contractor iOS exploits found on public websites and what it tells us about the crashing value of zero days in the AI era.

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Good morning, hackers. You are listening to The Lowdown, the best podcast about hacker stuff presented by Maze. Here with Matt J. and I am Low Level. We are in the PlanetScale office here at the AI Engineering Conference in San Francisco, having a grand old time talking about AI, AI security, and a variety of other topics. So Matt, what are we doing today, man? Why? Who put us on a plane? And who let two hackers physically break into a database company? the office are they aware what they've done are they aware of what uh what heist we are pulling

off here they gave us the wi-fi too that's right right i'm actually on the database company's wi-fi insane absolutely insane uh honestly i kind of forgot how cool silicon valley and san francisco specifically startup offices are i know you and i work uh from home slash little studios i used to live out here work out here i i forgot i forgot they've got that vc money they've got the swag. They've got the ping pong table. They got the podcast studio. They let us invade. It's been pretty sweet. They got a wall of mechanical keyboards that each of us kind of

nabbed out of one. Uh, it's pretty cool for planet scale to have us out here to talk AI security stuff during the AI engineering world's fair. I guess this is the second year of this conference, uh, over at Moscone center. Those of you, uh, that come to RSA every year, uh, Moscone center doesn't just exist during RSA. Uh, it doesn't just like materialize and show up just when 60,000 of us show up. There's about 7,000 people at this one. It's Moscone West, this secret third Moscone off to the side. It's a little smaller and quainter, but it's honestly, the vibes are good.

The vibes are high. Everyone's here talking about the same thing. Yeah. Yeah, the world of AI is in a weird spot right now. And I really acknowledge for the listener that we're going to talk about AI a lot. But specifically as a security person, it's becoming a topic that is so hard to ignore. Now, if you've watched my YouTube channel, you will know that like a year ago, I did not like AI. I was very anti-AI because the code that it writes was garbage and it couldn't find bugs. So like what use does it have for me as a security researcher or, you know, a developer?

Right. But I think with with the production of like Sonnet 4.6, there's kind of like this this break where like suddenly it was very good. And I'm not only producing code, but finding vulnerabilities in code. And today, like the models are a faster reverse engineer than I am. So I'm trying to figure out like where I fit in the world, like with that truth. It's a roasting a panel that I actually at PlanetScale to talk with the panel about like, what does the world of security look like with AI as a tool? Right. What can you do as not only an engineer or security researcher, but like a developer, right, to make your your your infrastructure, your code base more and more safe?

So, yeah, it'll it'll be could be a good panel. But interesting stuff, man, like like Fable recently got banned. What's going on with that? I mean, that's a whole can of worms that I'm personally very scared about. I'm curious to hear what you have to say. Yeah, I don't know if you realize you're sitting in the presence of a signatory of the free fable open letter. It's basically the Declaration of Independence. That's pretty rad. I put my John Hancock on it. So, yeah, obviously, the marketing has worked to some degree of that mythos and fable are going to escape the lab and they're going to be the super hacker.

Right. And you see this crap coming out in the headlines coming from some senator talked to somebody at the NSA that said that this thing could hack anything. It hacked all the NSA's confidential systems within minutes. And it's way too dangerous to be out there. And it's just I mean, anyone who knows what they're talking about knows that that's like not actually what's going on with any of these tools. Like, yes, as you just acknowledged, they're very good at code and they're very good at finding vulnerabilities. and the the thing that sets mythos and fable apart from the opus four sixes that turning point that

you're talking about is not just being able to find the vulnerabilities but actually write exploits for them which is the whole mythos thing and why we're talking about it so much and they've made this project glasswing and invite certain people to the walled garden to like get the super secret exploit creator thing and then fable was the public version of that with like laughable guardrails like we talked about it on our first episode i think right where like you couldn't even say the word cyber to the damn thing without it being like, you're going back to Opus. Like you can't, no, you can't say the word cyber in Fable land right now.

And so, uh, yeah, I mean, of course, if you market it as this day, dangerous, basically nuclear weapon, the government's going to, you know, get a little spicy and get involved. And so they've, they've, uh, invoked an export control is actually what they did. Right. So they didn't ban it. They said, they didn't say that you and I couldn't do it. They said that people not from the U.S. couldn't have access to it, which effectively, Anthropic has no possible way to enforce, like, upon the public, right? There's just no way. A lot of their employees currently cannot use their own tool under the current

regulation that came down. So this is like, you know, we're getting kind of sick of living in unprecedented times, but it's another unprecedented thing, right? And so, yeah, there's this free fable movement going on. Uh, Alex Stamos, ex CISO of, uh, Facebook and Yahoo and, uh, you know, just overall cyber, uh, thought leader, I guess he'll probably hate that I called him that, but, um, has been championing this. And, and a lot of the people that sign it, uh, the letter even says, Hey, it's not that everyone on this list agrees or disagrees about AI

regulation. We all just think that the way that this all went down is kind of crazy because Fable and Mythos aren't unique in their ability to find and even hack vulnerabilities. They've just gotten caught up in the marketing and hype of it. I mean, it's still going on. I just read yesterday that another, I think it was another senator closed our session said that they saw Mythos drain bank accounts in front of them. And it's just like, no, that's not how security tools work, right? That's not like maybe it found a vulnerability.

Sure. But it's not like, oh, this tool went out and drained the bank account or that's not like yeah yeah the secret hacking tool escaped the lab again what's really confusing there okay there are a bunch of confusing points in this whole this whole scenario the first part is like people don't realize i think that any good researcher that knows how exploitation works can take the primitives that another model like opus 47 or whatever finds and turn them into an exploit that is the thing that mythos is uniquely good at

is chaining primitives together but once you have the primitives when i say primitive i mean like arbitrary read arbitrary right like use after free whatever um you can turn those into a meaningful exploit like that is that is not a hard problem obviously the ability to do that automatically and chain them is scary but like you can find bugs right now with opus 48 force for whatever whatever whatever one is active and free you can plug it into gager mcp and find bugs and close software or go use it on open source software or or like sorry but shocking you could find an exploit these things without ai right exactly but regarding ai though what makes me nervous is

we're banning mythos because something something something or banning fable something something because it's really dangerous at finding vulnerabilities right i'm concerned that that opinion is being held in the ineptitude of government and once somebody who's smart in government and trust me they do exist there's not a lot of them um says hey guys we can find bugs without mythos and fable you know that right it is the solution to that problem then that we just get all the models banned like is it there and then illegal for someone not within the glass being bubble the government bubble to have access to a model capable of exploitation

right because again the the models were never designed to find bugs they were designed to write code so that the models could be profitable and then by being able to reason about a code base well oops it also is very good about reasoning about vulnerabilities and code bases yeah and And it's actually a really good point because one of the ways that some of the government officials are suggesting the next steps are is could you make the model less good and knowledgeable about security vulnerabilities? We want it to be we want you to be able to use it to code.

We just don't want you to be able to use it to hack. Right. Because that's scary. We don't know about it. And it's like, if you follow that train of thought, it's like, then the code would be filled with security vulnerabilities. If you could, could even possibly manage to suck the security knowledge out of these models, which is impossible, right? Of like, oh, you know, use after free or memory safety or whatever it is. So we'll know, like, of course it needs to know how to use memory safely because good developers know how to use memory safety safely. right so i actually think it would probably be worth it if uh we could take a second and actually

read some of the points on this free fable letter uh basically verbatim right because i think it's i think it's worded really well we could show it on the screen uh on the cut but i'll read it for the audio version right so there's a list of things on this letter it's a very short letter that um i've added my name to um and i'm probably bullying low level to do the same but um it says first we would like to state some things we believe ai is having significant impacts on cyber security Like, if you're not in that camp anymore, sorry, that ship has sailed, right? AI is having significant impacts on cybersecurity, including by greatly reducing the difficulty of finding flaws in software and writing exploits for those flaws.

Mythos class models are quite good at finding flaws and weaponizing exploits. However, they are not uniquely good at these tasks. This is, I think, the point that you and I are both making right now, right? And many of the undersigned individuals regularly use other foundation and open source models. We'll get back to the open source models in a second for security audits and red teaming every single day. Anthropic built multiple protections of the fable to the point of it was humorous to the cyber community because you literally said the word cyber and it kicked you out. And this was still good enough for them to pull this off the shelves.

it's essential to provide ai to coders and security teams so they can find and fix flaws in their own newly written as well as decades of legacy code i think this is the point i want to pause on for a second this is like my most strongly held belief on this topic we've had this conversation before metasploit is a tool that's open source and filled with exploits metasploit is this open source tool it's filled with exploits it makes exploitation easier right It's like lowering the skill bar of exploitation.

You don't need to know how to write a buffer overflow. You need to know how to point Metasploit at a thing and say, find CVE, hack CVE. A generation of pen testers have made a career off of just wielding a vulnerability scanner and map and Metasploit. And we've had this debate before of, are we lowering the skill bar for exploitation too much? And the answer is no, because otherwise you're just pretending like it's not possible. this is the same argument by the way for the listener if maybe you're not even a cyber security

practitioner here if you've seen the movie harry potter this is literally the defense against the dark arts argument right the ministry of magic decided that teaching how to cast evil spells was bad because you shouldn't do that and then the students didn't know how to defend against it and harry created this whole band of people that were learning it in secret but it's the same exact argument right like in order to know how to defend against these things how to have a meaningful security posture, you have to know how hacking works. You have to be able to find and exploit the vulnerabilities yourself so you can know how to then defend against them.

So the thought that you're able to do coding and security as separate tasks and you can just plop one out of the model is such a uniquely government senator congressman take that it's almost hilarious to see that written down. You mean this is coming from the people who said, excuse me, TikTok CEO, can you access my Wi-Fi, right? Mr. Chute, does TikTok access the home Wi-Fi network? Like this is the kind of people writing this stuff, right? But yeah, like we've settled this debate.

Giving defenders the best tools is the best course of action, period. End of discussion, right? Otherwise, you're just ostrich in the sand pretending like this capability doesn't exist. And it does. And the next bullet on this list is the like one-two punch to that because the Chinese open weight models are only months behind the best American models, not to pull the China boogeyman right card that a lot of people like to do in cybersecurity. But it's true there. They're out there. And not that the boogeyman is true, but but this part point is true that they have these open weight models, the deep seeks, the Kimmy K2s, the GLM 5.2s that are like on the

heels of the frontier models capabilities in this space. Alex, who wrote this, gave a talk recently, And he said that they're at most, at most 12 months behind the Frontier models in terms of, and when we say open weight models, we mean models that you can literally download and run on your own hardware and just circumvent any like regulation or guardrail or whatever it is that might be in place. So and these are whatever models that the Chinese government is even telling us about. Right. So it seems likely that the PRC government has access to private capabilities beyond

what it has published. And I think that's just very, very safe to assume. Right. Yeah. And to put the pull the best capabilities away from defenders without a good reason when our adversaries are rapidly advancing is dangerous. Right. So I just love this list. I think it was worth reading verbatim. I think the other point that I started to make, right, was not everyone on this list thinks that like, hey, hands off government, don't touch my AI. Right. I think some people probably think that, no, this is a scary paced technology.

Right. The pace of change is very rapid. And the capabilities that it is launching are sensitive. but there's four things on this letter that they say hey if you're going to regulate models then the regulation should be one grounded in scientific evaluations developed with input from the industry and academia to created through a democratic rulemaking process three enforced transparently and fairly with appropriate time given to remediate it right that did not happen at all

this was just a letter that popped out anthropic had to yank this stuff off the shelf because there There's no way to limit this whole export control thing. And then four, used only to the minimal extent necessary to ensure the safety of American public. And I think these are all pretty reasonable asks out of this. Yeah, 100%. Again, it just goes down a scary path that if the government, not really knowing much about anything, decides to pull one model, what says they're not going to pull the rest of the models? Oh, and also this model is Chinese and open source. That's also dangerous. And we can go into talking about the Dario comments about open source models, about how

Now, Dario, you know, the CEO of Anthropic says, yeah, open source models, because, you know, there's no control over them, just like, you know, open source hacking tools, etc. are uniquely dangerous and should also be heavily regulated if not banned. The meme being maker of closed source models says not closed source models are dangerous and should be illegal. Yeah, entering entering very dangerous territory. I have the same opinion. It's like I acknowledge that this is a huge shift in the tectonic plates of like the foundation of security, of cybersecurity, of security research.

But to just remove the average person's access to it is very, very knee jerk and definitely not democratic. Right. Yeah, I think the Dario thing is super funny. Right. It's like, of course, the head of Anthropic is like, whoa. And I'm also I'm seeing a lot of even cybersecurity leaders hop on that comment as well. I'm not sure I fully understand, you know, especially when the open weight models you can run on your own hardware, your own cloud hardware or anything like that.

It's not like you're necessarily just, oh, I'm going to now use a Chinese frontier model on their hardware. Right. These are open weight models. um there's obviously some concerns about they're not exactly free from their government regulations either over there so there are some things to be concerned about when you're putting those kinds of models in decision making loops uh for your organization because you do have to take in to account like the biases and regulations of the chinese government that's putting that stuff out

yeah when uh deep seek first came out it was like a meme to ask it about tiananmen square and like the deep seek model would uh not comment so you know go any deeper if you want to on that about like you know making wartime decisions or making some kind of vulnerability research decision on maybe a chinese platform right it gets um very scary very quick what you know the the amount of power that a a model developer has over over people in general this applies not only to china but like to anthropic to open ai anyone who's in charge of a frontier model wields unprecedented control over literally humanity very scary stuff yeah i think i mean i think it's kind of impossible

to take specifically frontier american models leadership's word on the dangers of open weight models i mean you know there are some concerns but uh i don't think that a lot of those concerns are necessarily uh handled by using the frontier models instead right like oh, you can't see inside this. Well, I can't. I don't know what's going on inside Claude, right? Like, you know, it's like, oh, a lot of these risks are just risks of using LLMs in

general, not necessarily just the open weight models. So I don't know. Ironically, and kind of the similar funny fashion. I don't know if you've seen this, but Meta recently restricted the use internally. This is came in from a leaked internal memo, restricted the use of quote unquote competitor model data, referring to the models that are made by OpenAI and Anthropic, because, quote, there could be legal implications if this data is leaked into our models or potentially

poisons our models. Yeah. So the funny part about that is what are the legal implications of all these companies having stolen quite literally in some cases, literally all of the planet's data to train their models why why is it only illegal if you get caught as meta doing it but if other companies do it to make their models like function it's not illegal there's this whole open-ended question about like is it even legal for anthropic to have the models in the current way that they argue and there's like literally i think we have receipts of maybe it was open ai like like taking

books that were like pirated online and using them to train their models i think i saw somebody demo how you could literally get one of the models to recite almost word for word like harry potter and the sorcerer or something like that second harry potter reference of the podcast yeah so it's uh very interesting that suddenly we're really worried about the legal implications of models with if ai gets caught with the bag anybody else is like now you're fine or sorry if if meta does rather yeah this this brings up some interesting points and thoughts for me you know we're seeing

a lot of internal enterprise restrictions popping up like about uh ai usage in general because it was like a free-for-all for a while right it's like hey no one you're not allowed to write your own code anymore like you must be ai super pilled 100x engineers and then all of a sudden everyone got the bills in the mail at the end of the quarter and they were like oh hey slow down on that token stuff everybody real quick uh and a lot of these restrictions are coming out um the The other bit about this is just like it's the meme of the surge projector like plugged into itself, this whole industry, right?

Like I saw, you know, I was talking to some people here that run some Neo clouds, which is even like a new word for me of these, you know, little mini clouds that are purpose built. And some of these is some of the AI companies are using because GPUs to that scale were hard to get for so long. So a bunch of people started hoarding them and there's all sorts of companies popping up for it. And you go and read some of these Neo cloud testimonials and it's like Google and Microsoft and whatever. It's like, oh wait, those are cloud companies. Like they sell compute in mass and they're using other cloud company.

Like I said, search projector plugged into itself. 100%. So now you get it not just in compute, but in AI model usage. So like, oh yeah, what is Google and meta and Microsoft and whatever? like what is their stance internally about using other models they're all making their own models right amazon made their own model like everyone's making their if you're a company of a certain size everyone was like we got to make our own model right and now like yeah you look at meta is is at the point of training their own model that they're actually worried about their employees

using the frontier models not just for like legal exposure but they're also worried about the quality they're in because they're like wait now we're like training on training output and it's like starts to become you know the watered down it like incest meme of like oh this is not actually high quality stuff anymore yeah this is the argument about like the overall in slopification of the internet right as more and more user generated content comes out of llms and then those llms are trained on user generated content you literally like like by definition have

a circular process uh the question becomes like what does that boil down to right what how how low can the quality bar get before we realize, OK, there is a structural issue with the way that we're producing information? And yeah, to your point, I think companies, maybe the smaller ones that have less blindfolds on, less blinders on, are starting to see that, right? There are some companies that are being like, hey, these tokens are extremely expensive. Oh, not even small companies. AWS recently or Amazon pulled down their internal company leaderboard for token maxing because,

oh shocker uh incentivizing your employees to use tokens for the sake of using tokens is a expensive and b not productive at all and aws again i ran by amazon for a long time with basically zero outages has had their two or three biggest outages in the last couple of years uh you know correlated but not maybe causated by ai so yeah have you seen did you see the meme it's like uh the hall of fame of useless statistics and it was like lines of code written in a day story points

closed in a day now it's token yeah now the lines of tokens used right i mean it's totally yeah it's totally true right it's you can't be like oh look how many tokens they spent that's how productive they were right it's like oh no there's tons of ways to just like waste tokens i think recently added to that leaderboard was also like git commits because we have people that are just like using claude in a loop and it's like literally the guy that created open claw or or whatever and then a levels io or like the number two like one and two on the github uh commits leaderboard like obviously they're ai people you know what i mean that's how it's going to play out now friend of the show zach corman uh was tweeting about kind of dunking on open

claw and the maker responded to him like hey can we stop dunking on open claw like yeah there was some security issues but like it's been four months and like microsoft is rolling us out now and then the replies were like microsoft famous for never rolling out security vulnerabilities like yeah oh in four months wow you must have solved it like all security solved yeah when uh when uh satya was at the conference where he said like they were going to integrate open claw into windows i saw so many sub tweets on that of literally like five months ago microsoft

being like open claw plenty of vulnerabilities unsecure like don't use it so yeah oh how the turntables with open ai is involved there's there's one more interesting point on this meta bit um i pulled up this article, right? That right at the end, and it's kind of like snuck in here, buried the lead a little bit, right? But it's like, it says the forward-looking question is whether Anthropic and OpenAI can build enterprise-grade deployment options that satisfy the data residency requirements of AI-native companies. And at the end, they kind of squirrel an editor's note that says, watch whether Anthropic and OpenAI respond with on-premise

or air-gapped deployment options. This is, I mean, this like my spidey senses went ding because I used to work for a large bank, Bank of America. I don't care, I can say it, it's on my LinkedIn. But, and this was like a major, major thing there, pre-AI, right? I got hired there to be like head of cloud security architecture. And then I walk in the door and I was like, oh, basically every policy document here says don't use the cloud. Like, it's like all data, all the bank's data need to stay in the bank you can't send data over there that's not the bank

right and so a lot of large enterprises have these like massive massive like policies compliance regulations government regulations whatever it is that say like your data and your customers data cannot go touch that other system without xyz like million controls in place i know some cybersecurity startups that i've been talking to that are really kind of behind and they feel they feel scared that they're falling behind on the whole AI curve because they have contractual obligations with government contracts that say that none

of that government department data can touch an AI thing. And now the company's like, well, we can't like buy for, we're not big enough to like have gov cloud at our company that like, Oh, those contracts only touch this copy of our system. It's like, no, their system is their system. We're going to be nearly acquire like an H 200 rack for $250,000. Right. Or like, we don't have that kind of money. Right. And so their option right now is to just not. And so now they're like, well, crap. Like, are we, you know, how many years behind the curve now? Because we are like contractually obligated to not use these kinds of coding systems because of these contractual obligations.

So this is why my Spidey senses went up is like, oh, yeah. Like, you know, that snuck in at the end of this article that like Meta is not going to be the first one to publicly say, hey, we can't do this. I'm sure the big financials have like whole little research teams off doing cool AI stuff. And then the rest of the employees, like multiple hundreds of thousands of employees at the U.S.'s biggest banks are not allowed to use these tools. I'm sure. Right. Unless they have like their own internal copy or something like that. And so, yeah, it's gonna be super interesting to see what they spit out that the enterprises could actually use.

Yeah. Yeah. Take away for the for the viewer, for the for the listener. I mean, it's it's an interesting world out there. I don't think there's too much dooming to be done yet. I think the AI is still in a very like transitionary state. We're trying to figure out what to actually do with this technology. Right. In the world of finding bugs, it is scary where the regulation may go on AI. But I think the best thing you can do is like maybe a practitioner. Go play with them. Go, go, go and use the models. Well, first of all, go download one before they're illegal. But after that, go, go use the model to see if you can find some bugs. Go, go see what they're capable of doing. It's really neat to see them operate.

whatever you think about like the the efficacy or the ethics behind ai watching them operate and like find bugs or like like reason about a code base is honestly like magical to watch it operate so i highly recommend everyone at least go go give it a shot and see what you know what uh what messes you can find yeah that's right i mean this is what i said about the free fable thing right is like you know you can't ostrich your head in the ground and pretend that this isn't happening just because you have like feelings about some of the stuff going on which was me by the way like i literally was that way up until like opus four six and i was like okay maybe it's time to try it

out and i did and i was like wow it's actually really impressive i had a lot of similar opinions to you but i was still kicking the tires on this stuff all the time just not on anything i cared about right i was just like trying to keep up with because like all the harnesses that are coming out right now like there's like the new hot word because a lot of the capabilities at the most most frontier models that are super expensive or banned by the government you can replicate a lot those capabilities with the right harnesses around some of the still available and cheaper models and these these kinds of harnesses have existed for a while to try to especially pre-opus 4.6

when the quality sucked and that's what you were seeing and a lot of us that were like really really staying at the tip of the spear were like yeah i get it but at the we're not using the out of the box models we're using the out of the box with like three different tools layered on top of to make sure that, you know, it was before loops were cool. Like we had stuff that was looping. We, you know, all sorts of stuff. There's, you know, been this community of kind of hackers doing a lot of this. And so, you know, that's all still going on. And so, yeah, I just like, we can't pretend that it's not. We have to get our hands on it to just like see what the capabilities are actually materializing.

100%. Hey, hackers, before we keep going, I want to take a quick break and say a quick thank you to our sponsors. Today's Lowdown episode is sponsored by our friends over at Maze. Maize has spent the last couple of years using AI to find and remediate vulnerabilities in the cloud. And now they've released Maize Code, AI agents that find and deeply investigate vulnerabilities in your code. Now, we all know the deal. Software composition analysis tools and SaaS toolings are all historically really bad at just making more noise. They find issues that may not actually be real and just create a lot of problems for your engineers to deal with that don't solve real security vulnerabilities.

I get it. We've been there. MaizeCode is a really cool tool because MaizeCode actually knows how your code works. MaizeCode investigates every finding with the context of how your code is actually deployed. Sure, you're using a version of libxml2 that's vulnerable. The actual code path to hit that vulnerability is not exposed in your Docker image. MaizeCode can find that and won't show you that that vulnerability is a big deal. Every vulnerability that MaizeCode reports comes with evidence that it's real and a way to fix it. Check out maze at go.lowdownpod.com slash maze.

That's go.lowdownpod.com slash maze. Thanks again, maze. Let's keep going. All right, we promise we'll stop talking about AI. We'll move on to a couple of bugs here and there. So interesting bugs found actually in the Apple Beats by Dre, a vulnerability in the Bluetooth stack that allows you to, what is this? Get remote code execution on a pair of headphones. Interesting sentence I just said there. How is that possible, Matt? what are we doing? Yeah, I covered this one in a video last week because anytime I've seen these bugs before, like on AirPods or other headphones and the public does not like these because guess

what? Like we're all like sticking speakers and microphones to our head. Most of the day I walk around my, I mean my, my AirPods are like my most used piece of technology. I walk around with an AirPod in a lot of my day. And when you have a security vulnerability in a microphone and speaker attached to most people, they tend to not like it, right? They're not like, oh man, can't wait for this hacker to listen into the microphone. And that's what this vulnerability would have allowed, which is kind of crazy. The caveat being, of course, with a lot of these Bluetooth

vulnerabilities is you did need to be within a physical range of the device that you were hacking. That's not really like a warm and cozy, you know, if someone goes to a conference like this, we're filled with 7,000 people and you can walk around with a nice antenna in your backpack I mean, these were the DEF CON of old vulnerability, like hacks back in the day, right? Or even like RFID, early RFID things that would ping off of random antennas and stuff like this. But yeah, you do need to be within range of it. You're going to be way better at talking about the actual vulnerability.

The one point that I will bring up before I toss it back to you is that this vulnerability was discovered a year ago. Yeah. So we can talk about kind of the nature of the bug and like the disclosure timeline. So like I said before, this bug, it gives you remote code execution on any device that uses a specific Bluetooth chip and Bluetooth SDK in particular, the software development kit. It's called the I'm going to pronounce this wrong, potentially AirOA, the word Air O-H-A, Bluetooth Audio SDK. The way that it works is literally the researchers that found it found a protocol that is implemented in the firmware of this controller.

They called it the RACE protocol. I'm not sure what that acronym stands for. And it's also not like the real acronym. It's what they made up about this protocol. But effectively, it is a hidden, non advertised service on the Bluetooth chip that is meant to be for debugging the device. It gives you the ability to do arbitrary memory reads to RAM, arbitrary memory writes to RAM and the ability to do over the air firmware updates. And you can use that information to leak the Bluetooth key about the device. You can use that to connect to the device without pairing to it properly and ultimately use it to initiate phone calls.

Listen to the microphone data on the headphones while they're paired to another device. You basically get total control over the headphones. Kind of a fun fact. You also could push a bad firmware update and brick the device. You know what you get from bricking headphones of a friendly neighbor. And I really couldn't tell you. But yeah, it's a scary attack. and this is kind of what you said before like the only attack nowadays that really matters when it comes to like proximal stuff like if you're at defcon and you're afraid of getting popped or things like this it's the low level it's the name of my youtube channel um the the low level vulnerabilities in the firmware of controllers like your wi-fi controller your baseband controller

your bluetooth controller these are the areas that get the least attention from people because the density of the skill set of people on planet earth that know how to like extract this stuff find bugs exploit them is increasingly low. Again, to mention AI again, I apologize. This is why AI is being touted as like this vulnerability research tools because they the models not trying to personify them, but like are really good at like learning about a specific technology, you give it a binary and say, hey, this lives inside this microchip, it can deduce bugs like

this. So yeah, there have been patches that have been fixed that have fixed this. The reason this broke the news by the way is um you know one of the line of apple headphones and not airpods but the the beat studio buds that apple now produces uses this uh this this chip and uses the sdk and therefore was vulnerable to it the patch just came out a about a week ago at this point june 19th the interesting part though going back to the the disclosure timeline the researchers of the the researchers that found this vulnerability found it in march of 2025 they didn't get contact

from the SDK developer until May of 2025. And then they worked with various manufacturers that make headphones that use this SDK. So it was like Sony, Marshall, a couple of other companies to figure out how they can quickly put out updates before going into closing this live at 3.9.C.3, something chaos convention. It's a conference that happens. It's a hacker conference. And so, you know, that went live and then Apple kind of kicked it off and made it more public by not pushing out a patch to fix this vulnerability.

in these beats so you know take away for the viewer if you use a um a headphone that uses sdk and you've been using them since i mean basically since this vulnerability came out the the timeline for when the vulnerability got created no one really knows but we definitely know someone knew about it the researchers in march um there is a world where your headphones could have bad firmware in them and could be doing evil stuff to you what does that mean maybe maybe you get new headphones maybe you make sure your firmware is patched um a couple courses back from there. But yeah, these kinds of firmware updates, I always hate because it's like, we can't we can't

get people to hit the restart my browser button, right? Like, these kinds, they should get updated automatically. Like if you're connected to power and within Bluetooth range of your phone or your computer that it's paired with, I've definitely I remember a few AirPods vulnerabilities very similar to this. And I remember being pretty frustrated trying to get the damn thing to catch a firmware update and there's like no interface you know it's not like you can push buttons on your airpods and like get it to like update right it's like okay the thing said plug it in and leave

it near my mac and i remember taking me like a few days to like i was like okay i gotta like leave this plugged in next to this like okay let me unplug it let me restart my phone or restart like just a lot of just weird troubleshooting and checking the firmware settings and i wasn't catching the update. I think even that scenario, like you were lucky in that you were trying to update a piece of hardware that lived within the Apple ecosystem. I would imagine if you're in the Sony ecosystem or like I think there was one line of Bose headphones. If you don't have like the Sony app on your phone or the Bose app on your phone, you're probably not getting an update from

these companies unless you go and seek it out by installing the app and running it. And again, if you're listening to this podcast, you're a security conscious person. A lot of people on planet earth aren't and they're not going to update the firmware on their headphones right so there's going to be a lot of people walking around planet earth that uh will still be open to this right so kind of a scary thing and yeah we'll never get stats on this one because you can't scan the internet for this is a proximity thing so we'll never really fully understand like well was that patch like successful and rolling out automatically to people like at a at a large

enough clip like this is like a decent one to you know keep in the arsenal uh you know if you're a pen tester or something like that to see what's what's out there and what's in people's pockets. Yeah, I this is a frustrating what we can't get people to update the firmware on their Wi-Fi routers that are like very sensitive to over the Internet attacks. Never mind like, oh, let me check my beats firmware settings somewhere in some, you know, hidden menu. It's just not going to happen. Right. Yeah. The you know, the adage of, you know, the S in IOT stands for security

continues to live on not necessarily the headphones or iot but it seems that like anything embedded tends to have bugs again i think the reason being that they tend to have the least amount of eyes on them and so the least amount of scrutiny unfortunately yeah i mean these are these are this one was also kind of a cool poc that they released because it was also um able to initiate and receive calls and also read off of the memory of the device which apparently actually did include some like call history uh type information on your head like you just wouldn't think right that my bluetooth headphones might have a copy of my call history

or the ability to initiate phone calls and stuff like that but of course they do right if you hit the you know they have tap functionality or whatever it is anyway kind of a spicy one in my opinion and especially it's been out for a year before the patch even came out and this poc dropped a while ago too i'm shocked this didn't get more attention i feel like this would be a thing you'd hear more about i mean it's proximity because it's proximity yeah but still go to a conference like defcon my point being there is like that's kind of the only bug that matters anymore is like this kind of attack like this if you connect the defcon wi-fi you're actually fine like literally unless you have like an unpatched windows 10 box you're gonna be a-okay but a bug

like this is like actually a big deal it's probably the most watched network right like the knock there have you ever taken a tour of it i mean then it's probably got the most eyeballs on it with the most talent density of spotting shitty behavior like on any network at any point so yeah you're good people bring burners or whatever no you're fine right but yeah this is kind of spicy I mean, I'm not even thinking about DEF CON or like a crowded environment like that, super targeted towards like government officials or people that might bring their headphones in a pocket into a room with insider information that might move the stock market.

Like, I mean, like microphone attacks are spicy and especially ones that would not really throw a lot of detections like that. You know, if you have to pop someone's laptop to get access to their microphone. Good luck. Right. Right. uh but what kind of edr is going to fire on your beats rce right uh ed's headphones are beaconing to china what's happening right now like yeah kind of spicy the psc was actually pretty gnarly too and in in like exfiltrating the info and eavesdropping on conversations and call history

and all that so uh kudos to the researchers to to even release like a polished psc like that too yeah 100 all right what's next speaking of researchers uh nightmare eclipse is making is making waves. You can talk about that. What, yeah. What don't we want to talk about on nightmare eclipse? So this one, I think this is the story that just keeps on giving. And I think there's more to it than the public knows. Um, I've talked to a fair few people that might have some inside info on this one, uh, that basically have given me the, like,

I can't tell you anymore that you're not, you don't have all the info. The news doesn't have all the info. There's lots of stuff going on. And if you read between the lines in Nightmare Eclipses, like comms and blogs that he's putting out, it's obviously like in turmoil, right? In like, there's much more going on between him and Microsoft than we know about in the blogs. And Microsoft being a big corporation can't exactly come out and be like, well, you see our lawsuit that's going on over here. There's some rumblings that they're actually an insider or they were an insider. And so I think that I've heard from a few credible sources that

that might actually be a possibility but there's be missing context by the way nightmare eclipse is a researcher that was on github and for fun they dropped at this point like six or seven windows defender or some kind of windows zero day that give you a local account to system escalation the reason they're dropping these zero days is apparently they tried to submit a couple of these to msrc the microsoft security response center which runs the microsoft bug bounty program right So a bug like that where you can escalate from one account to the other.

Actually, technically, MSRC doesn't respect the the admin to system boundary. But if you're like a normal user, they will pay you for an LPE. Apparently, they submitted these bugs or at least one of them to MSRC. MSRC said, nope, does not meet the bug bar. Sorry, you know, they don't give the money to the for the bug. And they said, OK, F you. And they they kick it off to the rest of the world. Yeah. As Matt was alluding to before, there's some rumors that that person may be a fairly young because you can kind of read in the way that they write be in some kind of turmoil, like financial or otherwise, because they said like they're living out of their car because of Microsoft

and Tom Gallagher, who was like the lead of MSRC, right? You know, calling him out. So, yeah, definitely not the most stable person. You know, you can read that from not only their text, but also dropping seven zero days publicly for fun. But yeah, so the most recent one is Rogue Planet, which is a pretty interesting exploit. If you are a defender and you're listening to this, There actually is no patch for Rogue Planet right now at the time of this recording. So if you want to look for the IOCs, we'll put a link to maybe an article that has them. But basically, it's a vulnerability in a race condition in Defender, right?

So Microsoft Windows Defender is the called EDR antivirus that lives on Windows. And so when Windows is scanning for viruses, if it sees a file that is potentially malicious, what it's going to do is scan the file, put it somewhere for quarantine, do more research on it do more more uh scanning on it and then go put it back okay well the time in between it taking the file and putting it back there's a race condition where you can put what's called an op lock and windows operational lock so that windows defender gets blocked on its operation and effectively the exploit replaces the now considered safe file with a piece of malware

and then uses what effectively in windows is a sim link to point the temporary directory back to system 32 and then bada bing bada boom microsoft defender is putting malware over a legitimate Windows service. So you use the Windows Event Manager in the example, but you could use any system level service. So race conditions are alive and well in the year of our Lord, 2026. And yeah, there's no patch for this right now. The IOCs, companies like, for example, ThreatLocker put out, or you can look for programs that are not Windows Defender

using the Windows Defender DLL is like the main one because they use that API to do the scanning and the replacement of the file but a crazy exploit not only just to exist but like to be dropping publicly for free yeah you you explain this to one to me before we hit record and it just blew my mind right that that the exploit actually just holds the file in place before defender can like do the defender thing on it i mean yeah that's that's sick that's just like really creative uh stuff yeah the the nightmare eclipse saga it's i've heard it described

as painful disclosure uh you know you've got responsible disclosure and then what's going on here is painful it's just like one after the other of these public pocs dropping i also read this one uh is this the same one i don't have it on my screen where uh the poc that they put out was for windows uh 10 and 11 but it actually does work on windows server they the nightmare eclipse said this poc will not work on windows server but this vulnerability does exist you just need to go tweak

the poc yeah so the way that the poc that's public works is they give you an iso file that is mounted as read only and you trigger the uh the actual vulnerability on the iso but then you make like a non email like a writable copy locally and use that to do the junction exploit right so the reason it's not vulnerable on server is you can't mount isos as a non-privileged user on server but i imagine through some other file system voodoo you can make a file that is read only somewhere copy it somewhere else effectively what i'm saying is you don't need the iso i believe

to make this vulnerability work because at the end of the day all the real vulnerability has nothing to do with the iso it has to do with the time of check time of use race condition in defender checking the file and putting it back where it found it um and so if you can figure out a way to execute that without the need for an iso file the server is fair game too yeah i think uh the the larger picture here too besides this i mean a bunch of these exploits have been super cool the psc i mean yellow key was crazy right the bitlocker stuff um these this is obviously a talented researcher and like you said obviously you know going through something right um legally

going through something from what it seems like as well. But what it's brought to light, and I think we've talked about this a fair bit on camera, both of us already, but like the reputation of your bug handling team, it should be considered sacred for security teams. So yeah, obviously, Nightmare Eclipse isn't the only game in town when it comes to being able to find exploits in large enterprise products. And I think the larger picture here is that the reputation of your bug handling system and team like MSRC should be considered sacred for security teams out there

because what this has brought to light, I know we both have kind of beat this to a pulp on camera before, but the community has collectively experienced a lot of pain interacting with a lot of these large enterprise bug bounty programs or even just disclosure processes. and Microsoft being one of the bigger ones, right? They have a very large code footprint out there on the internet and on hardware and everything full of code that is, let's say, target rich, right?

In terms of the kind of vulnerabilities that we're talking about. And over and over again, the researchers seem to be running into a few issues. And I think the security community is pretty used to this being a difficult process because it's a hard one to get right. is at scale having to go through this triage process. Have you ever lived it? Have you ever had to triage a bunch of output from tools? Oh, yeah. That was my job before I quit my last job exclusively. It's horrendous. It's painful, right? And so I think we all understand that I've been on both sides of this.

I've disclosed bugs to bug bounties. I'm an early Google bug bounty receiver, right? And I've been on the other side triaging findings of both scanners and humans. The quality varies greatly, right? So I think there's a certain tolerance that the community has to understanding what the other side of this is like. But the thing that keeps happening that I think people are starting to revolt against due to the, you know, maybe Nightmare Eclipse is a match being thrown into a powder keg of like pent up frustration around this issue, not even just Microsoft, right?

We're seeing very similar stuff come out about Apple and their handling of things and some other programs, other big programs is when a bug gets disclosed, the process is hard, slow, painful, not very communicative, any combination of the above. then the response is lackluster so either you get marked as a duplicate with very little information or you get marked as not actually a severe security issue and then the one-two punch that

i think is what's getting specifically msrc in a lot of trouble is and then fixing the vulnerability anyway right and then not crediting the researcher uh for it right and that's what i think is going on here yeah that is the the difficult balance of this yeah so from a timeline perspective i understand the timelines because yeah the amount of reports they probably get and the amount of people that they don't have to triage these varying quality vulnerability reports of a bug that may or may not actually be real especially with ai creates you know an internal uh inertia

to solve the problem so i heard on that 100 but it does get very hairy where it's like okay like this is a real bug in the software our company is incentivized to have a better product but also like because of what the bug bounty contract legally says we don't have to give you any money so what do we do with that and yeah microsoft's got caught with their pants down multiple times on not not acknowledging the researcher in the cve 60 days will go by the cve comes out the bug is fixed and they don't hear anything they'll get an email back right which obviously is not the right answer um so it's it's a difficult balance and uh microsoft

has not been very good at at finding this the center point yeah and i think i zoom out here not just to like dunk on MSRC or anything like that. It's more just to say like, this isn't going to be it. Like it's not going to be nightmare eclipse is going to be the only person out here publicly disclosing POC is for stuff because the responsible, which I'm putting in air quotes because the responsible part is a two way street. And, and there's like a social contract there of like, Hey, the agreed upon path now is you've broken your side of the social contract.

The agreed upon path is the community is public disclosure. to like get you to act right. Like, or just to acknowledge for the security of the community that the bug exists, right? That's kind of the whole point of disclosing like, hey man, your laptop has a vulnerability in it, figure it out so you don't get hacked, right? That's kind of the whole point. Yeah, the goal here is for us all to have a more secure internet and devices, not for like the multi-trillion dollar corporation to have like a good day and like the cheapest, quickest path possible to like whatever it is that they're doing, right?

That's like not our incentive, right? Our incentive is, hey, I found a bug that can like cause some serious pain on the internet. You wrote it. I'm now telling you about it. Like, let's do this whole thing and like get this fixed. And instead, it's like, like I said, slow, painful, no credit, bug gets fixed anyway. It's like, okay, what am I doing? Why am I on this side doing this? You a favor. Yeah. There is an incentives problem too, where I think with, again, AI, sorry, with AI being as prevalent as it is as good if i find any bugs it is um the market value of these bugs is going

to shift dramatically right like part again like you should be doing it for the love of the game for the love of the internet right but like people have to pay their bills and so a lot of people do this for money and if you can find a vulnerability in hyper-v or in windows defender or whatever and you get paid a hundred thousand dollars for it of course you're going to go and do that but if people now get paid maybe a thousand dollars because like everyone's doing it now like where does the incentive go? Do they now go to the black market and sell it for the same value? Do they now just go public and become an influencer because now they can get that kind of clout with a bug like that, you know, and then does that make the internet less secure over

time? Right? Yeah, I think I mean, and even the black market or whatever, like we're seeing, I recently covered and talked to the researchers who found Karuna and Dark Sword, these two iOS exploits, and they called it a $40 million exploit kit that was just on a watering hole website, not even targeted on like a Chinese crypto scam website for one of them and like a Ukrainian like dating site on another. And, you know, these are the kinds of things that usually governments point at specific individuals like political opponents, dissidents, journalists,

unfortunately, like stuff like this. And they just like put it out on a website. And like, that's why these researchers were able to just find it and like, you know, Ari it and do all the stuff that they did with it. And I asked them pointedly, I said, did they not know what they had or did they not care? And the researchers that I verified said, I don't think they cared. And they're like, what does that tell us? Does that tell us the value of a $40 million exploit kit is approaching zero for them to be able to just do that? Do they think that they can dial up another iOS zero day

or 23 of them that were in this exploit kit? Like there was 23 exploits under Karuna's umbrella that like chained it all together to do these zero click things, right? You go to a website in Safari that had Karuna on it they had rce that's good that's not one vault right that's a chain of bones yeah by the way guys gray market value for one of those exploits is like four to eight million dollars yeah so the whole thing they said it was i i've never heard people speak about an exploit kit the way i've heard really smart people talk about karuna uh the words like elegant and beautiful and like i mean

they were just fawning over this exploit kit and if you guys don't know the background it was written by government u.s government contractors l3 harris and trenchant and then leaked and the guy who leaked it is in jail. Yeah, this is the one, the L3 Harris guy that sold it to a Russian, right? Yeah, yeah. So a Russian exploit broker, who then sold it to both Russian buyers and Chinese buyers. So it wound up on this Chinese crypto scam website. Like I said, I mean, they couldn't have been brokered for that much money then at that point. Because of how it was then used,

right? There's no way you're spending $40 million to use it on like a crypto scam website, right? that's like not going to return that and so yeah are we starting to see the tips of like the exploit even dark market crash right and value is super interesting it's like oh yeah where's the where's the economics of this all go if ai gets really good at writing this stuff yeah 100 i'm sorry i'm not going to apologize every time i say yeah i like you yeah yeah i know it's just the nature of the beast right it's a reflex from youtube because uh my youtube audience is not a not a huge ai fan you know i get it and i do get the revolt right everyone's like

permanent underclass scared and like everyone's like oh the other thing that i'll just say like can we go on a tangent here really quick because we keep apologizing for it so like i i am of the camp that all these companies that are doing tens of thousands of layoffs under the guise of ai are full of shit right like so everyone who's like anti-ai because it thinks it's gonna like eat everyone's jobs and like all the water on the planet i think all of these things are actually not happening. I think these giant mega corps just have to do those layoffs so often or not

have to, but like do those layoffs so often. And they just, they, the reason they come in waves is not actually like a macro economic thing. It's a PR thing. It's like, they're all peers of each other. And like, if Oracle can point to Microsoft and go, well, yeah, look, AI and the economy, that's why we had to cut 30,000 people. And not that like, Hey, by the way, like if we can keep revenue here and like corporate ozempic ourself down to like here and get rid of like 15 of our most expensive thing which is you know our capex right on like all of these people like

why wouldn't we do that and the pr case is well yeah of course ai right because they want to seem like they're at the forefront there's no effing way i know the people at the like tip of the spear of ai and especially at those kinds of organizations there's no way they're like taking 30,000 jobs worth of output and, and like justifying AI. I will say at like a small scale, companies that like can't afford to like startups and like smaller companies are definitely running a little leaner these days and maybe not hiring that like social media person because they're

just, well, we'll have AI generate our LinkedIn posts until we can afford a real person because they realize the quality is lower or like, Oh, we're not hiring that role. Like, you know, they're pinching pennies in the smaller side i just think i don't know i maybe it's tinfoil hat of me but i i think on the large enterprise side all right i agree bananas i run tinfoil hat on most things whenever you think you have the answer for why a large entity is behaving a certain way you probably don't know the full story yeah so like i don't know if that helps the like anti-ai crowd for like looking at the thing that they think is going to like eat all

the jobs i just don't think that that that's like coming i think that's all like i don't think that all of the ai stuff is all marketing right i get i get yelled at a lot by like people on the internet because i am talking about mythos capabilities and exploit development and whatever and they're like you're falling for the marketing and i'm like hey listen i'm not going off of dario's right press release i'm going out off like project glasswing members like who i know and respect in this industry are like oh this thing found rce like while i slept right yeah you can acknowledge that like it could be marketing and it also could be good or it could be somewhere in the middle

where like it's just a yes they are go they're obviously using this to like generate a little bit of fear and then at the same time it is a better model objectively but like and like what happened they got banned because their marketing was so good right so like you know yeah people bought their marketing and they marketed themselves into a regulation situation anyway i don't know if that like calms ai nerves or whatever as we talk about it but like probably not but and on that note we'll wrap it for those of you listening we do appreciate it follow us on Spotify hit subscribe on YouTube and what are our closing remarks Matt what should we be doing

what's the next play um I think just in general just want to say like we we started this I don't know should we should we like pull the curtain back a little bit like stuff going behind the scenes we recorded a few episodes of this by the way but we we caught some attention of of some sponsors and stuff like this and we had to pause and like get everything together we're gonna we're we're doing this like we're here in person to like do this we're gonna do this at least weekly uh we've committed to it we're like looking to grow the team to help us behind the scenes i mean yeah so if you're here and if you've lasted this long you're you've at least heard of

us and you're here and you're chilling um we want to hear what you want to see out of this we're gonna have we have we have already like two or three exciting guests lined up we're going to start doing some interviews uh those you go to black hat and defcon we're going to do some cool sit uh you know stuff in vegas live shows and interviews and stuff like that so if you're here be here it's going to be cool um we're we're kind of joining forces low level and matt jay right like the the youtube conglomeration here um and and yeah let let us know where you're listening to this i want to know are we we're obviously doing youtube first but we're it's a

podcast it's our first like official podcast as a bunch of youtubers and instagrammers um so i want to know if people are listening on like podcast apps stuff like this reach out where we we read the stuff that you guys send our way both good and bad this is a very personal like an interaction right you're listening to us talk to each other for over an hour and i want to know what your take is like what you took away from this what you liked and didn't like we love feedback so please give it to us and we'll uh see you all next week all right

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Java4Shell, NGINX2Root & the Week Everything Went Down

    Nov 20, 202658 minAudio

    Recorded Wednesday, November 18, 2026. Java and NGINX had a bad week. So did anyone trying to catch a flight. The Low Down Podcast is presented by Maze. https://mazehq.com/lowdown X: https://twitter.com/Maze_Security Ed...

    Credit the people on this episode

  2. This SSH Bug Accepted Wrong Passwords, AI Exploits, Tiny Keys & a Surprise Guest

    Nov 17, 20261 hr 11 minAudio

    Recorded on Friday, November 13, 2026 The Low Down Podcast is presented by Maze. https://mazehq.com/lowdown X: https://twitter.com/Maze_Security 257 A's should not get you into an SSH account. John Hammond joins Ed and...

    Credit the people on this episode

  3. Binance's Fake Interview Hack, Railway's AI Incident, Hacked Freezers & a Critical Linux Bug

    Nov 6, 20261 hr 6 minAudio

    The Low Down Podcast is presented by Maze. https://mazehq.com/lowdown X: https://twitter.com/Maze_Security The "signup test" was probing for Kubernetes secrets. Ed and Matt get into Railway's AI testing incident, hacked...

    Credit the people on this episode

  4. Black October Recap, OpenCode’s Stolen API Keys, AI Distillation & the LiteLLM Supply-Chain Attack

    Nov 3, 20261 hr 24 minAudio

    Welcome to The Low Down, the best show on the internet for hackers Black October has real bugs, stolen keys, and a lot of very loud headlines. Ed and Matt sort through PHP2Shell, AI security claims, and the difference...

    Credit the people on this episode

  5. Cybersecurity Experts REACT to the php chaos... (and MORE)

    Oct 28, 20261 hr 28 minAudio

    Welcome to The Low Down, the best show on the internet for hackers Listen on Spotify! https://go.lowdownpod.com/spotify The Low Down is presented by Maze. LinkedIn: https://www.linkedin.com/company/mazehq/ X:...

    Credit the people on this episode