home.social

#bluehammer — Public Fediverse posts

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

fetched live
  1. EVERYONE GETS AN LPE

    Windows:
    #BlueHammer (#CVE_2026_33825)
    #RedSun (#CVE_2026_41091)
    #UnDefend (#CVE_2026_45498)
    #WindowsInstaller (#CVE_2026_27910):

    Linux:
    #CopyFail (#CVE_2026_31431)
    #SSHKeysignPwn (#CVE_2026_46333)

    FreeBSD:
    #FatGid (#CVE_2026_45250)
    #ExecveBug (#CVE_2026_7270)

  2. #BlueHammer wurde zum 14. April 2026 als Defender Schwachstelle gepatcht. Hier meine Nachlese samt Link auf eine Fortra-Analyse.

    borncity.com/blog/2026/04/16/b

  3. Pissing off a hacker is never a good idea. The #BlueHammer researcher has dropped another one, abusing Microsoft Defender's dorky behaviour to gain NT Authority privileges.
    github.com/Nightmare-Eclipse/R
    #Security #Microsoft #Windows #RedSun

  4. Fully exploitable Windows Defender vulnerability with full source code public for >8 days no CVE assigned so far (BlueHammer).

    Writeup: hackingpassion.com/bluehammer-

    Full source code: github.com/Nightmare-Eclipse/B

    /cc @bsi Was ist eigentlich der "Prozess" für vollständig öffentliche Lücken zu denen es seit über einer Woche noch nicht einmal eine CVE Nummer gibt?

    Edit: Patch and CVE number CVE-2026-33825 available by now. Took 6 days though.

    #infosec #itsec #Microsoft #WindowsDefender #BlueHammer

  5. Recently this popped up, #Bluehammer a #Windows exploit that exploits Windows Defender for a local privilege elevation

    From user to system level..

    It triggers a Defender scan and locks that after, so it can access a certain database that is been backed up while Defender scans to gain system level access

    GitHub now gives a warning for the repo it seems:
    github.com/Nightmare-Eclipse/B

    Just be careful

  6. @wdormann Of course Microsoft used their GitHub ownership to remove the repo instead of fixing both problems (the exploit and the video requirement).