home.social

#tarmageddon — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #tarmageddon, aggregated by home.social.

  1. This episode of #OpenSourceSecurity I chat with Alex Zenla from Edera about the #TARmageddon vulnerability they found

    I've coordinated a lot of vulnerabilities in my day, but never have I had to even think about something as difficult as this one. Alex fills us in on how it was found, what the coordination looked like, and some things to think about as we manage these incredibly complex supply chains

    opensourcesecurity.io/2025/202

  2. 🪤 TARmageddon (CVE-2025-62518): RCE Vulnerability Highlights the Challenges of Open Source Abandonware

    「 In the worst-case scenario, this vulnerability has a severity of 8.1 (High) and can lead to Remote Code Execution (RCE) through file overwriting attacks, such as replacing configuration files or hijacking build backends 」

    edera.dev/stories/tarmageddon

    #TARmageddon #CVE202562518 #rust #rce #cybersecurity

  3. Rust async tar libraries are affected by a High 8.1 severity vulnerability CVE-2025-62518 “TARmageddon” which allows potential RCE and supply-chain attacks.

    forum.hashpwn.net/post/5906

    #rust #cve_2025_62518 #TARmageddon #tar #cybersecurity #news #hashpwn

  4. So apparently #Tarmageddon is a thing…

    While the RCE claim seems bullshit, going by what I’ve heard about it, it wouldn’t have shocked me, given how much
    unsafe people use in practice, but that isn’t the interesting thing here…

    The notable thing is that this is in a widely used unmaintained dependency, making it the exact kind of issue I’ve been warning about for ages and one of the prime reasons I still can’t really get myself to use
    #Rust: Instead on focusing on a small number of well maintained, highly established packages like for example Boost (in C++), everything is its own crate, mirroring the hellscape that is node and when you complain about it, the defense is always version pinning.

    Guess what: Version pinning
    prevents updates to newer versions that contain fixes and especially doesn’t help with unmaintained software!

    Rust has a decent (but not perfect!) technical foundation, but the culture around it really is something that repels me every time…

  5. Ah, the joys of #open source! 🤦‍♂️ #TARmageddon strikes with a #CVE number longer than a CVS receipt, proving once again that "free" code is never free from #hilarious mishaps! 🎉 Who knew #parsing #bugs could be this entertaining? 🙃
    edera.dev/stories/tarmageddon #source #mishaps #HackerNews #ngated

  6. Distro maintainers working on the #Tarmageddon / #CVE_2025_62518 you might like @niklaskorz work 💚.

    He started to compile a list of software that includes one of the vulnerable crates in its dependency tree, based on the current state of #nixpkgs. You might find affected packages in your own repositories.

    github.com/NixOS/nixpkgs/issue

  7. While the bug in async-tar/tokio-tar dubbed #tarmageddon / CVE-2025-62518 is cool on a technical and code-correctness level, I'm calling bullshit on the #RCE claim. It's a severe overstatement that isn't backed by the advisory.

    Processing a tar stream with a vulnerable version won't execute code on your computer. Even unpacking it to disk won't lead to RCE or overwritten configs.

    The claim is that a security scanner would interpret the tar file differently. That's not what RCE means. #Rust

  8. Not quite #Tarmageddon, but another example of an unpleasant #anthropocene unconformity😠.

    Recent #Targlomerate overlying #Lewisian reworked migmatites; so an age gap of getting on for 2 billion years🤪

    Luckily this was an exception on an otherwise pristine #Hebridean coastline

  9. Not quite #Tarmageddon, but another example of an unpleasant #anthropocene unconformity😠.

    Recent #Targlomerate overlying #Lewisian reworked migmatites; so an age gap of getting on for 2 billion years🤪

    Luckily this was an exception on an otherwise pristine #Hebridean coastline

  10. Not quite #Tarmageddon, but another example of an unpleasant #anthropocene unconformity😠.

    Recent #Targlomerate overlying #Lewisian reworked migmatites; so an age gap of getting on for 2 billion years🤪

    Luckily this was an exception on an otherwise pristine #Hebridean coastline

  11. Not quite #Tarmageddon, but another example of an unpleasant #anthropocene unconformity😠.

    Recent #Targlomerate overlying #Lewisian reworked migmatites; so an age gap of getting on for 2 billion years🤪

    Luckily this was an exception on an otherwise pristine #Hebridean coastline