←
AndrewMohawk⁽ⁿᵘˡˡ⁾13,113 posts
AndrewMohawk⁽ⁿᵘˡˡ⁾ avatar

AndrewMohawk⁽ⁿᵘˡˡ⁾

@AndrewMohawk

Sec/Madness @privy_io principal security , @_seal_org technical council prev: HoS @uniswap, D&R/IR @RobinhoodApp, IR @BitMEX, Built @Paterva Maltego with RT

◷ Joined February 2008▧ 1,066 Photos and videos
AndrewMohawk⁽ⁿᵘˡˡ⁾ avatar
AndrewMohawk⁽ⁿᵘˡˡ⁾@AndrewMohawk·11 Dec 2025

Fun react bug, (CVE-2025-55183) if you have a server side component and it explicitly or implicitly exposes a stringified argument you can get the source code for that function. Also found DoS, but reported it to vercel instead of meta and some else reported the next day 🙃

Post attachmentPost attachment
1:21
gabsmashh avatar
⟳ AndrewMohawk⁽ⁿᵘˡˡ⁾ retweeted
gabsmashh@gabsmashh·2h

we've officially run out of vulnerability names, so i made a generator to help us continue the proud tradition of naming everything Something2Shell. you're welcome. i'm accepting zero feedback. oops-all-shells.netlify.app/

AndrewMohawk⁽ⁿᵘˡˡ⁾ avatar
AndrewMohawk⁽ⁿᵘˡˡ⁾@AndrewMohawk·3h

IM SO TIRED

Pre-auth RCE in nginx is the bug every hacker dreams of finding. It almost never happens. Today we’re disclosing nginx2root: five nginx vulnerabilities, and an exploit that takes an unauthenticated attacker all the way to root. One of themhits the default config. If you run nginx, patch now. Then read: nginx2root.com CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425

AndrewMohawk⁽ⁿᵘˡˡ⁾ avatar
AndrewMohawk⁽ⁿᵘˡˡ⁾@AndrewMohawk·4h

ouch.

#Java4Shell #CVE-2026-114938 Achieving a full RCE exploit chain is quite challenging. Heap memory disclosure, on the other hand, is relatively easy to achieve. But the real danger comes when sensitive data, like AWS access keys or something, happens to reside in nearby memory regions. This is reminiscent of #Heartbleed back in the day.

Post attachmentPost attachment
Nicki Sanders avatar
⟳ AndrewMohawk⁽ⁿᵘˡˡ⁾ retweeted
Nicki Sanders@nickisanders·Nov 16

Ok, so L3Harris, the FAA's network contractor, was replacing old copper lines with fiber at a remote site in El Dorado, Arkansas. After a new router went in, it started sending more than 1,000 connection attempts every 4 to 5 seconds to other routers on the network. At the same moment, a second router in Amarillo, Texas, upgraded weeks earlier, began doing the same thing. That flood of traffic disrupted radio and radar links at 17 of the FAA's 22 en route centers. The network only stabilized after both sites were blocked. Hewlett Packard Enterprise, which owns the router's maker Juniper, says the device "functioned as it was configured to by the installer." The FAA has since disabled the suspect functionality on about 60 similar routers as a precaution. The reporting on the investigation is inconsistent. CNN reported the FBI took possession of the hardware. The FBI says the equipment is still with L3Harris, with agents at the company's Florida lab helping rule out a cyberattack. The open question is why two routers installed weeks apart failed at the same moment. The bigger lesson is that a national system shouldn't be able to go down because of one edge node.

BREAKING: The FBI has reportedly seized the router and other equipment the FAA says were responsible for the nationwide ground stop. Hold on a second… If this was simply a faulty wire or routine equipment failure, why the hell is the FBI taking possession of the hardware? Maybe there’s a perfectly reasonable explanation, but this certainly raises some eyebrows. What exactly are they investigating that the public hasn’t been told? Or let me guess, Kash Patel is trying to figure out a way to blame Biden.

0:40
watchTowr avatar
⟳ AndrewMohawk⁽ⁿᵘˡˡ⁾ retweeted
watchTowr@watchtowrcyber·Nov 17

watchTowr Intel is aware of public reports of an unauthenticated RCE in Java, CVE-2026-114938, affecting OpenJDK 17.0.6 and later. Details are still unconfirmed. Review your Java environments now and monitor for vendor announcements.

float avatar
⟳ AndrewMohawk⁽ⁿᵘˡˡ⁾ retweeted
float@notesbyfloat·Nov 14

"didn't you wear that yesterday" there's this thing called an L1 cache

Natalie Silvanovich avatar
⟳ AndrewMohawk⁽ⁿᵘˡˡ⁾ retweeted
Natalie Silvanovich@natashenka·Nov 13

As a result, we will be enforcing a 60-day deadline starting February 2027, and a 30-day policy starting January 2028.