• 0 Posts
  • 116 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle

  • I did. The article is scant, and the source report is everything bad about ai in the vuln world; high drama, low info. LPEs are not RCEs!

    And we don’t know what the exploits are. If it’s a bunch of local jvm consoles or vi escapes into shell where it’s like “oh this could give you root!”, that’s not super useful without knowing if it’s a dumb initial config or an actual use-after-free or other memory exploit.

    That’s why we don’t classify manufacturers with bad/no default creds as CVEs, that’s just bad

    Like I said, there is a lot of work to do before these become legit, and it almost certainly won’t be 958 exploits after actual professionals review them properly.

    And again, stop taking OpenAI at their word about security.


  • If you have ever actually seen the discovery process, you’ll understand that bugs and rce’s don’t just popup on a list from a computer. Sure, you can generate a list of places to start testing, but each of those has to be validated, reproduced, documented and understood before it’s confirmed. It’s not just the discovery of a starting point that constitutes an rce or other vuln, there’s a ton of work that needs to be done by humans also.

    So a few bad ones in the news? Sure. A list of 1500 non-validated rces? I’m not holding my breath.

    You really have to think critically and let go of the “hacker” sensationalism in infosec, it’s easy to fall into.




  • It shows that the CVE fixes were consistent during the last 2.5 years and 14 releases.

    Right, yes. But if the transitions from 4.x to 5.0 and 5.x to 6.0 were also shown, we’d be able to see that the bump itself isn’t significant, and that this happens after every major version release.

    The magnitude of the bump is what’s important, and we can’t see that without comparing to pre- and post- AI tooling.

    Why 5.0 and 6.0, those are ancient. This goes back to 6.9 from May 2024, where Ai usage in the Kernel wasn’t a thing until the recent few releases.

    That’s the whole point.



  • This is misleading.

    Edit: “misleading” was the wrong word. I was just pointing out that showing data from 4.x to 5.x, 5.x to 6.x also would have made this post more meaningful.

    Linux kernel full releases always have CVEs shortly after them because new features, drivers, memory handling tuning, and other capabilities arr introduced, and people (or ai) hammer away at them as soon as they appear.

    I acknowledge that the bump has more amplitude because ai tools accelerate this, but this graph isn’t the shocker you think it is.





  • Hey, you’re the one on the journey of de-googling, it’s your decision.

    However, one of the reasons many ppl degoogle is because we are lied to all the time by software companies.

    Iris keyboard also says “network permission is optional until triggered by translation”, and the iris keyboard immediately asks for network permission on install, so trust that as much as you like.



  • It’s more useful to consider a container an administrative separation, and as others have mentioned here, being vigilant means not trusting any one technology implicitly.

    Cgroups2 and libcontainer do a decent job now of separating child processes from host processes and resources, but with ai-assisted tooling will eventually come the discovery of more vulns and escapes at a more accelerated pace. In those times, when everyone is panicking, having cultivated other good security habits will bring you some measure of understanding what exactly your risks are.

    Containers are somewhat separated from the host os in a functional way, I don’t think your mental model is wrong, per se, but that separation shouldn’t be relied on by itself.


  • Connections to apple streaming source CIDR blocks, connections to apple auth CIDR blocks, and a bunch of ips in apple blocks I have no idea what they do.

    Apple domains are easy to identify. https://support.apple.com/en-us/101555

    A lot of it associated with iTunes and apple store stuff like mzstatic.com but also https connections to unknown domains. It’s almost all https, so impossible to say what’s being sent.

    The content streams are easy to pick out, because only a handful of stateful sessions go to known CDNs.

    Why starting a movie or show on an apple TV requires a check to siri and search is probably explainable, but certainly 1400 requests during movie play to diagassets.apple.com (the “diagnostics” domain known to be a black hole of Apple mystery) is probably reporting data of some kind.

    It goes on like that, mysterious connections that occur during video play and at startup to domains like Apple Education raise a few eyebrows.

    And then there are the plugins, which do a lot of phoning home.




  • Blueray have anti-copying built into non-data areas, plus Cinavia DRM on the content most of the time. This means your 1-to-1 copies won’t play.

    If you are hoping to make a playable bluray, use one of the tools that reads past both and creates a non-drm image.

    Depending on where you live, this likely breaks copywrite, but isn’t illegal.