Further correction
Far more than 52% of servers are vulnerable. But unique servers that I actually see people using — that actually have people clicking my tester link — this population is actually getting safer by the day.
Leave a Reply Cancel reply
Major Projects
Phreebird: Zero Configuration DNSSEC
Interpolique: Easy Cross Language Injection Defense For The Web
DanKam: Augmented Reality for Color Blindness
Security Talks
2014
Yet Another Dan Kaminsky Talk: Hard Drive Operating Systems, Storage XOR Execution, Secure Random By Default, Cryptomnemonics, Ending Use After Free in Browsers, Fast Spoofed DDoS Tracing, NSA Crypto Fallout
Slides
2012
Black Ops: Practical System-Wide Timing Attack Defense, Real World Entropy Generation For Devices, Safe String Interpolation, Image Loads For Censorship Detection, Certificate Extraction w/ Flash Sockets, Stateless TCP Sockets
Slides
2011
Black Ops of TCP/IP 2011: Bitcoin Cloud Deanon/Data Embedding, External Interface UPNP, TCP SEQ# Attacks Revisted, Generic Password to Asymmetric Key Generation, Net Neutrality Validation
Slides
2010
Introducing The Domain Key Infrastructure:
Zero Configuration DNSSEC Serving, End-To-End Client Integration w/ UI Via OpenSSL and Secure Proxies, Federated OpenSSH, DNS over HTTP/X.509, Self-Securing URLs, Secure Scalable Email (Finally!)
Slides
Code (Phreebird Suite)
Black Hat USA Slides
Interpolique:
Where's The Safety in Type Safety?, Preventing Injection Attacks (XSS/SQL) With String Safety, Why Ease Of Use Matters, Automatic Query Parameterization, How LISP Was Right About Dynamic Scope, Dynamic DOM Manipulation For Secure Integration of Untrusted HTML
Slides Audio
Code
Realism in Web Defense:
Why Security Fails, What's Wrong With Session Management On The Web, The Failure Of Referrer Checking, Interpreter Suicide, Towards a Real Session Context, Treelocking, The Beginnings of Interpolique
Slides
2009
Staring Into The Abyss:
Middleware Fingerprinting, Firewall Rule Bypass, Internal Address Disclosure, Same Origin Attacks Against Proxied Hosts, TCP NAT2NAT via Active FTP And TCP Spoofing
Slides Paper
Black Ops Of PKI:
Structural Weaknesses of X.509, Architectural Advantages of DNSSEC, ASN.1 Confusion, Null Terminator Attacks Against Certificates
Slides Video
Financial Cryptography Paper
2008
It's The End Of The Cache As We Know It:
DNS Server+Client Cache Poisoning, Issues with SSL, Breaking “Forgot My Password” Systems, Attacking Autoupdaters and Unhardened Parsers, Rerouting Internal Traffic
Black Hat Slides
BH Fed Slides (Adds Drupal, DNSSEC)
Video Audio
"Illustrated Guide To The Kaminsky Bug"
Sarah on DNS
Ad Injection Gone Wild:
Subdomain NXDOMAIN injection for Universal Cross Site Scripting
Slides
2007
Design Reviewing The Web:
DNS Rebinding, VPN to the Browser, Provider Hostility Detection, Audio CAPTCHA Analysis
Slides Video
2006
Pattern Recognition:
Net Neutrality Violation Detection, Large Scale SSL Scanning, Securing Online Banking, Cryptomnemonics, Context Free Grammar Fuzzing, Security Dotplots
Slides
Weaponizing Noam Chomsky, or Hacking with Pattern Languages:
The Nymic Domain, XML Trees For Automatically Extracted Grammar, Syntax Highlighting for Compression Depth, Live Discovered Grammar Rendering, "CFG9000" Context Free Grammar Fuzzer, Dotplots for Format Identification and Fuzzer Guidance, Tilt Shift Dotplots, Visual Bindiff
Slides Video Code
2005:
Black Ops of TCP/IP 2005.5:
Worldwide DNS Scans, Temporal IDS Evasion, the Sony Rootkit, MD5 Conflation of Web Pages
Slides Video
2004:
MD5 To Be Considered Harmful Someday:
Applied Attacks Against Simple Collisions Via Malicious Appendage, Executable Confusion, Auditor Bypass, Bit Commitment Shirking, HMAC Implications, Collision Steganography, P2P Attacks Against Kazaa Hash
Slides Paper
Code (Confoo)
Code (Stripwire)
Black Ops of DNS:
Tunneling Audio, Video, and SSH over DNS
Slides Audio
Code (OzymanDNS 0.1)
Code (OzymanDNS 0.1 for Windows)
2003:
Stack Black Ops:
Generic ActiveX, SQL for Large Network Scans, Bandwidth Brokering, SSL for IDS’s
Slides Audio
Code (Paketto Keiretsu 2.00pre5)
2002:
Black Ops of TCP/IP:
High Speed Scanning, Parasitic Traceroute, TCP NAT2NAT
Slides Audio 1 Audio 2
Code (Paketto Keiretsu 1.01)
2001:
Gateway Cryptography:
SSH Dynamic Forwarding, Securing Meet-In-The-Middle, PPTP over SSH
Slides Audio
SSH Cheat Sheet
Other Research
@dakami
- dear gen z we are so very sorry twitter.com/HVRanch/status… 1 year ago
- Close. AI has plenty of doubt (most models can return probabilities for any prediction, if you configure them to).… twitter.com/i/web/status/1… 1 year ago
Keep up the good work. A lot of us appreciate the huge effort you are putting forth to mitigate this issue.
Thanks for all the hard work on this.
Running the dns-oarc test repeatedly against a major telecom isp, they seem to have a lot of different servers and if I am interpreting this correctly, about 40% are patched at this hour. So maybe a bunch of folks are working late on this…
Hey Heard you on RadioLive, THANKS. Although you said Xnet’s servers were still vulnerable I used you checker and if I’m understanding it correctly I’m ok.
again thanks!
sir i have put a link on my website http://www.pcguru.co.nr
to your website to help people know about the vulnerability. Hope all our pcs are safe. many thanx for ur effort
thanks for your good effort and guidance………
Thanks for all the hard work on this.
We got our first server safe after a router/firewall upgrade (the dns server it self had already got the update before we found your test site).
the tester works great, but would be nice if there was a place to insert the dns server to test. 😉
I see a lot of people saying “it would be nice if you could put in the DNS server to test.”
The tester works by passively monitoring the queries from your DNS server. When you click on the link, your computer asks your resolver (whatever it is) and Dan’s tester just listens.
In order to let you enter the DNS server to test, the tester would have to ask your server to do the recursive lookups.
If it does, you’ve already flunked the test. Badly.
Sorry for my English.
Tanks a lot. My provider don’t upgrade the servers, and the connection isn’t safe.
I use openDNS.org. Very ok.
From Italy.
Bye
Antonio
Hi Dan,
It would be real helpful if the IP address that is being used for the DNS check is appended to the results.
I’m not sure which DNS the button is checking as I sit behind a firewall/router with three DNS IPs that could be used in rotation because of timeouts.
It so happens that for me, one of them is a major backbone DNS, one is the DSL specific DNS, and one is the DNS of the web hosting service that I use.
I’ve had DNS problems over the last several days – maybe because of patching – so it would be real nice to know which one is commonly being used.
Thanks for the good work. Also I love your sense of humor and having your daughter – very cute – do the YouTube bit. Not many experts are that real about themselves and that they can make a mistake in judgment about the best way to solve a major problem.
Best Regards
Here in Spain the biggest ISP (Telefonica) hasn’t patched the DNS servers yet, i’ve talked with some operators about that and they even dont know about this issue.
So, they told me to change to some other DNS server if i have some problems ¬¬.. the problem is that 95% of their clients use the default DNS server…and they dont even plan to patch it.. pathetic IMHO xD
Take back my prior comment about the DNS server IP as I had NoScript enabled on Firefox and it was blocking the results. Ooops. 😦
Rogers Cable (Canada) is an ISP that remains unpatched. I just found out now and currently using OpenDNS.
How do we get ours ISPs to patch? Phone and complain?
todayy i switched to Opendns and say it is secure and the ports are completly random.
Also i added some trustable ips to he host files to point to the right domains.
I did complain and my ISP did not know anything about this flaw and they won’t patch it, but i hope the 7th of August when Dan will release the full details and everybody have acces to it will patch the servers.
I don’t realy get why you did not show the details to the worls when you discovered because the half of worldwide ISP are full of dickheads.
Any updated guess on what percentage of servers are patched at this point (8/5/8)?