edoardottt🐘 retweeted
cariddi - Take a list of domains, crawl urls and scan for endpoints, secrets, api keys, file extensions, tokens and more. by @edoardottt2
github.com/edoardottt/caridd…
edoardottt🐘 retweeted
With so much CVE slop, @tldrcve is a way to validate if one is overhyped. It tries to determine actual risk on most configs.
It is also open source, so open a PR or issue to contribute: github.com/streichsbaer/tldr…
Great work by @s_streichsbier
OpenSSL base64 bug (CVE-2026-121481): the 9.8 is overblown.
It needs about 1.6 GB of input in one call; the only known trigger is a huge openssl s_client proxy password you set yourself. The 9.8 is CISA's, not OpenSSL's. Next patch cycle.
tldrcve.com/openssl-encodebl…
edoardottt🐘 retweeted
🚨‼️BREAKING: Clown2shell exploit where u where u umm play urself bcause u keep reading cveslop nd u think oh wow am i pwnd nd u keep trying to patch but it ddoses u nd that lets the hackers in bcause ur too busy juggling dogshit. read more on wiz blogpost
edoardottt🐘 retweeted
A lot of named vulnerabilities used to mean default config + internet = cooked. Today, we’re seeing some very cool bugs, but the fine print changes the picture a bit. Nice to see ASLR and other protections making mass exploitation harder.
Take the wins where you can, I guess.
edoardottt🐘 retweeted
The RCE for nginx needs 128GB of HTTP/2 traffic to trigger and specific CPU instructions to be exploitable
I hope I saved you some time.
edoardottt🐘 retweeted
Remember when a critical vulnerability meant you could actually get RCE?
Now it feels like every new *2Shell requires perfectly aligned planets, 17 non-default configurations, and a blood sacrifice to reproduce.
Can we just go back to bugs that are just... exploitable?
edoardottt🐘 retweeted
Honestly I’m tired of this AI discovered RCE bullshit.
It creates so much chaos inside of companies that have no idea how to deal with this.
Anyone that publishes an exploit that can’t be widely exploited and doesn’t disclose this - I’m down for total public shaming of the individuals and companies that push this narrative.
I’m not dismissing the criticality of latching on these - however it doesn’t require IR, all hands on deck, must patch tomorrow - which is probably why we see the mass outages we are experiencing.
It’s damaging our industry. We need to fight back on this and go after those that hype this up for ego and marketing.
POC || GTFO
Join me.
edoardottt🐘 retweeted
I think we need a new CVE barometer of what constitutes a 9 or 10 CVE for remote exploitation. Or at least a viability of how bad it could be, like an "oh shit meter".
Most of these 2shells require very specific things to be in play to work. They are still brilliant bugs no question, but companies shouldn't be created a critical incident for every single one of these that comes out daily or weekly.
We are going to destroy all trust in the cybersecurity industry if we keep doing this.
There has to be a better way.
.
Looks like Java4Shell will be a more limited affair, sourcing details from the @datadoghq writeup by @Frichette_n and Sebastian Obregoso:
1. Requires x86-64 CPU with AVX-512 VBMI. From what I can gather, this is most newer generation cloud instances that aren’t ARM. You can run `grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo` on the host to see if you’re potentially impacted.
2. It’s far easier to try and abuse this to cause a DoS than a full RCE. RCE must be targeted and is not generic.
3. Patches are out and two mitigations exist: starting the JVM with option `-XX:-UseBASE64Intrinsics` or a more breaking change `-XX:UseAVX=2` which reduces performance and will break ARM64 JVMs if it’s in a shared config.
4. The full exposure is really JDK 17.0.6+ on AVX-512 VBMI x86 hosts, with code that Base64-decodes untrusted input through the JDK’s basic or URL decoders.
I’d treat this as a high-priority DoS with a targeted RCE possibility, not a Log4Shell.
43
edoardottt🐘 retweeted
Prediction: java2shell will be just as bad as php2shell (which wasn’t that bad).
edoardottt🐘 retweeted
We are tracking a breach of a 3rd-party JS host impacting hundreds of high value websites.
This is staggering.
edoardottt🐘 retweeted
BREAKING: A cyberattack hit 178 major organizations, including Zoom, CNN, BBC, Fox News, HSBC, Ledger, Equifax, Salesforce, IKEA and Air France-KLM, by loading malware on the Optimizely Web platform, exposing visitors to scripts built to steal payment data and exploit iOS devices, per security firm Report URI.
Banking and finance was the hardest-hit sector, with 32 organizations affected, including the UK's HSBC across multiple markets such as the US, Hong Kong, Mexico, Singapore, Australia and the UAE.
edoardottt🐘 retweeted
This is a big one.
We found malicious JavaScript being served through Optimizely to some of the world's largest websites.
178 organisations affected, with everything from crypto theft and card skimming to iOS exploits.
Zoom, BBC, CNN, HSBC, Salesforce, GitLab, KLM, IKEA, Equifax, Ledger. The list goes on... Full list in the post.
blog.report-uri.com/worlds-l…
edoardottt🐘 retweeted
Holy cow, there’s a massive Microsoft outage going on. Outlook .com is down, globally, as I understand. Microsoft employees cannot send/receive email as well (plus everyone else using M365)
This is very bad given how important email is for comms
Postmortem will interesting
Any telegram message can now become RCE
6630b003766baed1fa86cea880d22e41dc416f63d800de3246941ede2396ad48
Any Telegram message can now become an app.
⚡ Downloads instantly (less than 4 KB)
🎨 Interactive and natively rendered
💸 Payments and viral mechanics built in
🛠️ Build your own. More info and docs for devs: t.me/BotNews/122
Thanks @intigriti for the support ❤️
Contributions are welcome! 🤗
Subdomain enumeration won’t show you every domain your target trusts... 👀
csprecon by @edoardottt2 reads the Content Security Policy of your targets and pulls out every domain it allows, from API hosts to CDNs and third-party services! 🤠
🔗 github.com/edoardottt/csprec…

























