Just checking in on all the MSMQ vulnerabilities in 2023 including #QueueJumper - from honeypots, I didn’t see a single exploitation attempt, just scanning.
There also still isn’t a proof of concept exploit that reaches remote code execution still. #threatintel
Four months passed since the publication of #MSMQ #QueueJumper.
Has anyone seen any in-the-wild exploitation yet?
Still seen no in the wild exploitation of CVE-2023-21554 aka #QueueJumper, from a wide variety of telemetry. Turns out not publishing an RCE exploit helps prevent exploitation.
Pretty funny easy query to know if #QueueJumper request is internet scanning or malicious - filters out internet scanning. A month since publication, I haven't seen any in the wild exploitation (even just crashing the service, which is ridiculously easy).
VMConnection
| where ProcessName == "mqsvc"
| where BytesSent <> 572
| where BytesSent <> 0
MDE AHQ for exploitation: https://github.com/GossiTheDog/ThreatHunting/blob/master/AdvancedHuntingQueries/QueueJumper.ahq
Accidentally deleted my #QueueJumper toots, but so far no sign of any in the wild exploitation, no technical write up and no public exploit. Monitoring with real world MSMQ, all quiet too.
Credits to CheckPoint for not providing exploitation details, has given orgs time to patch. Also kudos to not branding it a “cyber pandemic” this time.
We've been able to trigger CVE-2023-21554 AKA #QueueJumper, a recently patched RCE in Microsoft’s Message Queueing Service reported by Check Point. We can confirm it appears exploitable. IOCs and more: https://www.randori.com/blog/vulnerability-analysis-queuejumper-cve-2023-21554/
It's been a heck of a week, with tonnes of great research and tooling that I'm sure you're going to get a kick out of - check out our wrap-up for all the news!:
https://opalsec.substack.com/p/soc-goulash-weekend-wrap-up-16042023
Kaspersky researchers shone a light on the Dark Web trade in Google Play Loaders - a service to help inject malware into legitimate, and supposedly vetted apps, with guarantees of >1 week up-time and the option to boost your spread with targeted Ads.
#Nokoyawa ransomware have clearly got some talent on their team, having abused a #CLFS 0-day prior to Microsoft patching it last week - one of 5 different exploits they've used, mind you - and they appear to have a new, distinct ransomware strain in rotation, too.
There's heaps more great threat reporting, including a report that #FIN7 and former #Conti (#FIN12/#WizardSpider) members are collaborating on a new backdoor, and a crypto-mining campaign that may be the canary in the coal mine, indicating broader uptake of BYOVD and IPFS by low-level operators.
The #QueueJumper vulnerability from last week looks primed to explode in coming days, with a no-fix vulnerability in Microsoft Intune capping off a lousy week for Windows admins struggling to keep their networks secure.
TOOLING. Ooooh boy, this was a good week for tooling and tradecraft, ladies and gentlemen.
The #redteam have a new port of the SharpHound AD enumeration tool for Cobalt Strike; a great reference piece on leveraging stolen Office tokens to bypass MFA and access cloud workloads, and a list of keywords to avoid when crafting stealthy PowerShell scripts.
The #blueteam have a script to help tweak VM settings to circumvent malware anti-analysis checks; Procmon for macOS, and a lightweight bastion host to help redirect and record traffic sent to honeypots in your network.
This was a fun one to write up, with heaps of interesting reads and takeaways to be had. Get amongst it!
https://opalsec.substack.com/p/soc-goulash-weekend-wrap-up-16042023
#infosec #cyber #news #cybernews #infosec #infosecnews #informationsecurity #cybersecurity #hacking #security #technology #hacker #vulnerability #vulnerabilities #malware #ransomware #dfir #soc #threatintel #threatintelligence #darkweb #microsoft #azure #mfa #mfabypass #cobaltstrike #bloodhound #sharphound #byovd #ipfs #intune #GooglePlay #Android #zeroday #0day
Still all quiet on the western front when it comes to #QueueJumper. Had one connection that didn't appear to be an obvious (known) security researcher, from 216.250.119.94 - but benign.
btw Shodan has the best scanning hostnames
Jetzt patchen! #QueueJumper-Lücke gefährdet hunderttausende #Windows-Systeme | Security https://www.heise.de/news/Jetzt-patchen-QueueJumper-Luecke-gefaehrdet-hunderttausende-Windows-Systeme-8961420.html #Patchday
Done! Submitted a pull request to the #nmap project to add a #MSMQ service probe. Hope it gets accepted and helps everyone once merged.
https://github.com/nmap/nmap/pull/2632
Paging @shodan, you may find this useful. It's different from the one I posted yesterday.
#QueueJumper #CVE202321554 #vulnerability #vulnerabilityManagement
If the byte at offset 18 is set to 0x02 instead of 0x12, that connection request was actually accepted.
Ouch if you find this on the Internet I guess!
And since we're here... A comparison of #Censys and #Shadowserver's #MSMQ probes. They are using the same probe except for the padding.
How do I know all this? May have quickly set up a terrible #honeypot last night 😄
Just out of curiosity, a comparison of our probe vs the one I've seen #censysio is using.
The protocol is proprietary, so I have no ideia what theirs is doing 🤷♂️
@VitorHSSousa and myself have developed a #nmap service probe to identify whether a service on port 1801 is #MSMQ.
I've just published it on the URL below. We can't guarantee this will successfully detect every version, but we've tested with a few Windows Server and non-server versions and it seems to work across at least recent ones.
We hope this helps defenders identify exposed MSMQ so they can mitigate the risk from #QueueJumper.
https://gist.github.com/goncalor/a01ba66927c0dc704000d7bf1327d36e
#QueueJump #CVE202321554 #vulnerability #vulnerabilityManagement #patchtuesday #patch
Shadowserver and Shodan are recently very interested in 1801/tcp. #QueueJumper
I've managed to figure out a packet that if sent to a #MSMQ server results in a response that can be fingerprinted.
If you send this packet and the response contains LIOR and a bunch of ZZZZ this indicates the service is probably MSMQ.
I can't guarantee this works for all versions, but it works at least for recent ones.
I'm going to try to write a #nmap service probe for this service.
echo -ne '\x10\x00\x0b\x00\x4c\x49\x4f\x52\x3c\x02\x00\x00\xff\xff\xff\xff\x00\x00\x02\x00\x06\x55\x3d\x51\x36\xdf\xc7\x40\x96\x43\x17\x5c\x3c\xe7\x6c\xaa\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' | ncat -v 127.0.0.1 1801 | hd
#QueueJumper #QueueJump #CVE202321554 #vulnerability #vulnerabilityManagement
It would have been extremely useful if #checkpoint posted a basic way to detect #MSMQ remotely. No PoC, no nothing. Just confirming that's the exposed service on that port.
Damned be these proprietary protocols.
Does anyone have a way to remotely confirm the service running on port 1801 is #MSMQ? I've tested #nmap and it seems it cannot identify the service.
#QueueJumper #QueueJump #CVE202321554 #vulnerability #vulnerabilityManagement
The #QueueJumper MSMQ vuln is a great find. I don’t know if there’s much knowledge in InfoSec about MSMQ but it’s very widely used in middleware - eg pretty much all the main Siemens ICS products use it.
