
Developer, Hacker & Lover | Security Researcher at @Intel | Former @_CPResearch_ Vulnerability Research TL | Opinions are non-existent
Tel Aviv, Israel
Joined August 2009
- Tweets243
- Following274
- Followers1.1K
- Likes1.1K
Pinned Tweet
We released the technical details behind "Hacked in Translation" – from subtitles to RCE
blog.checkpoint.com/2017/07/…
Due to a schedule conflict, I have 2 tickets for the 37C3 conference available for sale. Available in DM. #37C3
ChatGPT doesn't only pass Turing's test, but would also slide into his DMs, tell him to meet them at the make-out point and then ghost him
4
I stopped maintaining CapTipper 4 years ago since the decline of exploit kits.
To my surprise, I learned the tool is still being used in DFIR toolkits and networking courses in colleges.
So I found some time to fix a few bugs and port the code to Python3:
github.com/omriher/CapTipper…
Omri Herscovici retweeted
A malicious picture can trigger an Instagram vulnerability potentially resulting in RCE on mobile devices.
Read our full technical paper here:
research.checkpoint.com/2020…
After 7 years at Check Point Research, I'm moving on to my next endeavor. Leading the vulnerability research team at @_CPResearch_ was an inspiring position, and it is truly one of the best places in infosec. See you guys down the road!
Omri Herscovici retweeted
[CPR-Zero] CVE-2020-6008, CVE-2020-6009 & CVE-2020-6010 (Learning Management Systems): Multiple critical vulnerabilities (SQLi + File Write) in the 3 leading WordPress LMS Plugins
cpr-zero.checkpoint.com/vuln…
cpr-zero.checkpoint.com/vuln…
cpr-zero.checkpoint.com/vuln…
We're getting asked whether the registry workaround for SIGRed works on Windows Server 2003 and the answer is YES.
However, if your organization still runs it there are probably multiple other ways to pwn it other than using CVE-2020-1350
Congrats @NetanelBenSimon for being listed on Top MSRC 2020 Q2 Security Researchers. well-deserved! @_CPResearch_
msrc-blog.microsoft.com/2020…
Turning ON Analytical Logs in Windows DNS could allow for the detection of the SIGRed vulnerability. Looks like the logging of the crafted SIG query is written even if the exploitation fails and the server crashes
this is an e.g. of MS DNS Logs (256, 257) for Query and Response, contains good info for hunting and detection (Packet details, QTYPE will be eq to 24 for SIG and res-packet size can be also deducted with some manips (if >64KB + maybe DNSEC!=1) ->
blog.menasec.net/2019/02/thr…
It seems that RRSIG-Records parsing indeed leads to the vulnerable function, therefore can also be used to trigger the vulnerability
This Post is from an account that no longer exists. Learn more
There are 40,000 internet-facing Windows DNS servers listening on TCP port 53, but for #SIGRed it could be much higher in case the server only listens on UDP 53.
You can force the target to initiate a TCP connection to you by turning on the Truncation flag in a UDP response
Replying to @shortxstack
I saw thay after this tweet. I will mention it tomorrow in the SANS Webcast: sans.org/webcasts/116120
Omri Herscovici retweeted
Thankfully I had wormable RCE on my 2020 bingo card! Nice find Sagi Tzadik! Windows admins: you have one job today. Patch.
We just disclosed SIGRed (CVE-2020-1350): Critical Vulnerability in all Windows DNS Servers (by @sagitz_).
Bonus: can also be triggered using the browser through a malicious link. #SIGRed
research.checkpoint.com/2020…
That's why we recommed simply using the following command for the SIGRed workaround:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters" /v "TcpReceivePacketSize" /t REG_DWORD /d 0xFF00 /f net stop DNS && net start DNS
But patching is much preferred!
Replying to @SwiftOnSecurity
Thousands of customers are going to create this registry key as a REG_SZ or screw up the DWORD data because it’s not documented fully, reporting tools are going to incorrectly say fixed, but this key actually does nothing, and now you’ve made it worse because no patch urgency.















