"The size arguments tell mbed TLS how many bytes to read from each buffer. The call uses sizeof(dhm_g) for both, even though dhm_g is only one byte long. The length for dhm_p should be sizeof(dhm_p), or 256 bytes.
As a result, mbed TLS reads only the first byte of dhm_p: 0xFF (255)."
We've seen this before. In 2022 I discovered a flaw in Arris-based routers (CVE-2022-31793) using strcpy() over a byte buffer of binary data, which often resulted in a predictable key that was used to encrypt SIP/router configuration credentials on millions of US-based home and small business routing equipment.
I predict we'll find many more of these as we audit cryptographic API calls for bugs in embedded devices / open source projects.
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing...
The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer.
- TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely.
- LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap.
- OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for.
These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure.
foxio.io/blog/choose-your-ba…
Derek Abdine retweeted
The server was hacked and someone exfiltrated the key. gg. news.ycombinator.com/item?id…
Someone has created a vulnerable PHP website, loaded it with a Bitcoin wallet, and challenged the Internet to hack into it and they can keep the Bitcoin. It has a running timer to show if the PHP exploitability was over-hyped. stealmybitcoin.com/
Derek Abdine retweeted
Update: Our PHP exploit is now production-grade.
* stock php.ini-production, display_errors=off, normal memory_limit, multi-worker, ASLR, under load
* ARM64 + x86-64 targets
* MediaWiki, WordPress, phpBB, Laravel
* Apache/mod_php and nginx/php-fpm -> root
xitter.cf/dguido/status/21131291…
Re: the widely circulated blog claiming the PHP bugs aren't easily exploitable: @trailofbits has a working exploit that gets a shell on an unmodified MediaWiki installation.
eliastaylor.com/noexploit/
Derek Abdine retweeted
Our team's (private) #php2shell exploit now supports:
- PHP 8.4.10 - 8.4.26 on AMD64 + ARM64 with ASLR
- PHP 8.5.10 and 8.5.11 on AMD64 + ARM64 with ASLR
* WordPress exploitation on default Docker installs running the above versions of PHP
vulncheck.com/blog/php2shell…
Why does everyone seem to think patching source code will solve security?
Once source code is patched, the compiled packages have to be distributed. That’s a much harder problem.
Source is the “easiest” problem to target because models are very good at it. Dropping a fix on a running application sever, container image, etc and testing that end to end is what a significant amount of IT and security have to deal with.
Derek Abdine retweeted
🚨 LiteLLM, a Python package for connecting to AI model providers with 92M+ monthly downloads, has been compromised.
Version 1.107.0 ships credential-stealing malware through PyPI wheels and Docker images, targeting cloud credentials, developer secrets, and AI tools.
Derek Abdine retweeted
OpenCode is currently under a sustained cyberattack, and mid-incident they ran into the same problem Hugging Face did: the frontier models they were using for defense began refusing to help fight attacking agents because analyzing the attacks started triggering safety guardrails.
Derek Abdine retweeted
Called it. Reverse engineering of mobile apps is now much easier and can be used to target their supporting back-end APIs, possibly using API tokens in the app.
The right design is an authenticity boundary, where reaching the APIs requires attestation of authentic, published Android or iOS app.
【注意喚起】国内で相次ぐ情報漏えい事案の原因の一つとして、新たな攻撃手法『A2B攻撃』を特定しました。
攻撃者は公開Androidアプリの解析結果をもとにバックエンドサーバを狙い撃ちしています。
Androidアプリを提供している事業者は要注意です。
#NICT #CYNEX #LETTICE
nict.go.jp/press/2026/10/13-…
It's humbling to see tools like REA being able to crank out reverse engineered code from libraries.
In the early 2000's, it took months of late nights and weekends to crank through identifying regions of memory of Grand Theft Auto to understand how the game worked, and find areas where we could extend it.
Models are ridiculously good and fast at doing this now. We're seeing that with this renaissance of game modding currently, but I expect we'll see it used more and more widely as we go along. There are other areas where this is useful.
That'll lead to unlocking all sorts of new creativity from previously closed source code. It'll also lead to better security, and better support for environments using software that is deprecated.
Derek Abdine retweeted
This is correct:
"Attempting to outpace AI-driven exploitation with reactive defense is a losing battle. As Provos noted in follow-up work on AI threats[1], security teams should focus on using security invariants to limit attack paths rather than trying to defend at machine speed."
okta.com/newsroom/articles/n…
[1] provos.org/p/security-at-mac…
Derek Abdine retweeted
Last week some of South Korea's biggest banks were hit by a cyberattack. Thanks to a report from CrowdStrike tonight, we now know the entire hack may have been done by a single person. He used a combined stack of an open-source AI penetration tool named ARTEX, DeepSeek v4.1-Flash, GLM-5.3, Grok 4.6, and Claude Code.
“Agents we believe to be operated by OpenAI made some unsuccessful attempts to compromise our public Etherpad, a note-taking tool we host as a community service.”
“… made millions of automated requests to our public APIs to access the knowledge on Wikimedia projects, crawled millions of pages (mainly from our projects Wikidata and Wikimedia Commons), and made hundreds of thousands of data queries to the Wikidata Query Service (WQDS). This traffic may have contributed to a partial outage on WQDS in May.”
In ethical security research, great care should always be taken, and it seems like there was an absence of it here.
Reference:
wikimediafoundation.org/news…
Derek Abdine retweeted
The economics of the cybersecurity attack/defense game have clearly changed when researchers are dropping what appears to be KVM/firecracker 0day on a max $50k bug bounty:
xitter.cf/PaulosYibelo/status/21…
I really don't think people are understanding the @HacktronAI HEIF Heist moment properly.
Before AI, what class of attacker do you think would be capable of discovering a silently fixed upstream image parser vulnerability w/o a CVE assigned nor patched in distro packages, exploiting against modern Linux w/ ASLR, and then using it to pop top-tier tech companies w/o them noticing?
I have *never* seen bug bounty researchers land something like that. Have you?
Derek Abdine retweeted
.@DarioAmodei and @sama!
it is high time you put some money into KYC, or whatever trust/verification system you want, and give legitimate security researchers access to your best models.
1. we’ve helped secure both of your companies multiple times against issues that could have had serious consequences. i wouldn’t be surprised if we can keep doing that, and i also wouldn’t assume every capable attacker is reporting what they find.
2. there is now a KVM escape that, if researchers hadn’t found it first, could have been exactly the kind of thing your models eventually find in another hugging face style incident.
you know, the list will keep growing, this is not the end.
it rationally makes sense to get as many trusted researchers and companies as possible red teaming your companies, your models, and the infrastructure they depend on.
Derek Abdine retweeted
Full VM escape zeroday (guest>host root in industry standard hypervisors)! More soon
Derek Abdine retweeted
Anthropic doing advertisment for GLM-5.3 was not on my bingo card: Anthropic says Zai's openly downloadable GLM-5.3 approaches Claude Mythos Preview’s exploit capabilities, with safeguards that are easy to bypass.
On ExploitBench, GLM-5.3 built working browser exploits in 50 of 410 attempts. Mythos Preview managed 56.
In a separate controlled experiment, researchers used GLM-5.3 to discover previously unknown browser vulnerabilities and combine them into a webpage that could read files from the test machine.
Anthropic also reports 64–100% engagement with malicious requests under different safeguard bypass conditions.
So yeah, interesting times ahead.
Derek Abdine retweeted
636606729769440499166579950236036751749912014371509557713570027508971809534551913252252094954941974952859310861988904737359709200557919
is a factor of RSA-896
saweis.net/posts/rsa-896.htm…
Derek Abdine retweeted
Cyber is having a moment
Across 21 major software companies, including Apple, AWS, Microsoft, and Google:
- Reported critical vulnerabilities never cleared 100 per month in four years
- Since spring they've jumped to over 600 per month
Charts of the Week: a16z.news/p/chart-of-the-wee…
Derek Abdine retweeted
This trend has been building for a while, and Glasswing demonstrated the risk early on. Now we need to get defense up to speed with offense.
Cyber is having a moment
Across 21 major software companies, including Apple, AWS, Microsoft, and Google:
- Reported critical vulnerabilities never cleared 100 per month in four years
- Since spring they've jumped to over 600 per month
Charts of the Week: a16z.news/p/chart-of-the-wee…