Binarly is the only company that developed the generic detection of XZ backdoor implantation and released a free detection tool and public API access (https://t.co/VeNtPledKh).
Current statics: 📈5000+ scans, 🚨76 unique variants of the #XZbackdoor detected!
Most of the other detection tools we have seen have focused on simple version checks, hash-based detection of the backdoored component, or YARA rules of the hardcoded unique string constants. All of these could lead to massive alert fatigue and false positives at scale by overloading security teams.
Anybody else wish that the underhanded coding competitions were still a thing? After all the XZ shenanigans I'd love to see some underhanded buildscript techniques. Though I still want C and a million other languages too.
What kind of prize would be enough to entice folks?
I've been reverse engineering the xz backdoor this weekend and have documented the payload format and written a proof-of-concept exploit for the RCE. The payloads are signed with an ED448 key, so I patched my own key into the backdoor for testing. :-)
https://t.co/CvKo3xPRkP
Can't wait for the first dynamo table that gets exposed and exfilled. 😨 Are we really sure knowing account ID's isn't important?
https://t.co/6jrR4bqDHC
Today we’re releasing weAudit, the VSCode extension we use during secure code reviews to collaboratively take notes and highlight code regions. https://t.co/e0ZnmknQjU
🗺️ TrailDiscover: Mapping CloudTrail events to Incidents
@Flekyy90 has released https://t.co/C8ZwOeRQ1h, an open-source mapping of 256 CloudTrail events to 50 known security incidents.
51.5% of included events have been used in the wild!
https://t.co/drMnl2yXnX
😈 Hacking Terraform State for Privilege Escalation
@dagrz demonstrates how an attacker with access to modify a Terraform State file can insert a malicious provider that will execute code on the next `terraform init`
+ mitigation guidance
https://t.co/iGbx2KyIeb
My method for spinning up replica domains and labs with ease! From client centric domains useful for testing evasive payloads; to testing the newest techniques in a range.
PoisonedRAG: Knowledge Poisoning Attacks to Retrieval-Augmented Generation of Large Language Models
(non-peer-reviewed)
"we propose PoisonedRAG , a set of knowledge poisoning attacks to RAG, where an attacker could inject a few poisoned texts into the knowledge database such that the LLM generates an attacker-chosen target answer for an attacker-chosen target question"
"our attacks could achieve 90% attack success rates when injecting 5 poisoned texts for each target question into a database with millions of texts"
paper: https://t.co/ODVX31d1xv
code: https://t.co/4Vu5gzekhE
We've witnessed attackers using new attack techniques in AWS:
• Creating a large number of ECS clusters for crypto mining
• Using EC2 Instance Connect for lateral movement
• Using AWS Resource Explorer for enumeration
https://t.co/AQgLB5K0Tp
This is by far the most interesting vulnerability I’ve found - a critical misconfiguration in GitHub’s runner images repository! Here is the full detailed write up:
https://t.co/25BxESuIj4
Did you hear, the November MilSec is just over a week away! 🎉
This month's MilSec Meet will be on Thursday, Nov. 9, at Pistol Pete's. If you're around Brookfield, don't miss out!
See you next week! RSVP here 👇
🔗https://t.co/APfVuU7jKR
#MilSec
Given that @pdnuclei has posted a full PoC for CVE-2023-46747, we're sharing the full F5 RCE blog post now. Link is https://t.co/6CWJ01Chk4. Shout outs to @iamnoooob@rootxharsh for getting the PoC in < 72 hours and to @OrangeTsai for the inspiration! #f5#cve202346747#nuclei
F5 BIGIP is vulnerable to a smuggling request vulnerability that an attacker can exploit to achieve unauthorized RCE. Our vulnerability research team responsibly disclose this to F5, which released a hotfix today. https://t.co/dSMv9w6ga9 #vulnerabilityresearch#f5#cve