Dan Kaminsky | |
---|---|
![]() Kaminsky in 2007 | |
Born | Daniel Kaminsky (1979-02-07)February 7, 1979 San Francisco,California, U.S. |
Died | April 23, 2021(2021-04-23) (aged 42) San Francisco, California, U.S. |
Alma mater | Santa Clara University[1] |
Occupation | Computer security researcher |
Known for | Discovering the 2008DNS cache poisoning vulnerability |
Website | dankaminsky |
Daniel Kaminsky (February 7, 1979 – April 23, 2021) was an Americancomputer security researcher. He was a co-founder and chief scientist of Human Security (formerly White Ops), a computer security company. He previously worked forCisco,Avaya, andIOActive, where he was the director ofpenetration testing.[2][3]The New York Times labeled Kaminsky an "Internet security savior" and "a digitalPaul Revere".[1]
Kaminsky was known among computer security experts for his work onDNS cache poisoning, for showing that theSony rootkit had infected at least 568,000 computers,[4] and for his talks at theBlack Hat Briefings.[3] On June 16, 2010, he was named byICANN as one of the Trusted Community Representatives for theDNSSEC root.[5]
Daniel Kaminsky was born in San Francisco on February 7, 1979, to Marshall Kaminsky and Trudy Maurer. His mother toldThe New York Times that after his father bought him aRadioShack computer at age four, Kaminsky had taught himself to code by age five. At 11, his mother received a call from a government security administrator who told her that Kaminsky had usedpenetration testing to intrude into military computers, and that the family's Internet would be cut off. His mother responded by saying if their access was cut, she would take out an advertisement in theSan Francisco Chronicle to publicize the fact that an 11-year-old could break military computer security. Instead, a three-day Internet "timeout" for Kaminsky was negotiated. In 2008, after Kaminsky found and coordinated a fix for a fundamental DNS flaw, he was approached by the administrator, who thanked him and asked to be introduced to his mother.[1]
Kaminsky attendedSt. Ignatius College Preparatory andSanta Clara University.[6] After graduating from college, he worked for Cisco,Avaya, andIOActive, before founding his own firm White Ops (later renamed Human Security).[1]
During theSony BMG copy protection rootkit scandal, whereSony BMG was found to be covertly installing anti-piracy software onto PCs, Kaminsky used DNS cache snooping to discover whether servers had recently contacted any of the domains accessed by the Sony rootkit. He used this technique to estimate that there were at least 568,000 networks that had computers with the rootkit.[4] Kaminsky then used his research to bring more awareness to the issue while Sony executives were trying to play it down.[1]
In April 2008, Kaminsky realized a growing practice among ISPs potentially represented a security vulnerability.[7] Various ISPs have experimented with intercepting return messages of non-existent domain names and replacing them with advertising content. This could allow hackers to set upphishing schemes by attacking the server responsible for the advertisements and linking to non-existent subdomains of the targeted websites. Kaminsky demonstrated this process by setting upRickrolls onFacebook andPayPal.[2][8] While the vulnerability used initially depended in part on the fact thatEarthlink was usingBarefruit to provide its advertising, Kaminsky was able to generalize the vulnerability to attackVerizon by attacking its ad provider,Paxfire.[9]
Kaminsky went public after working with the ad networks in question to eliminate the immediate cross-site scripting vulnerability.[10]
In 2008, Kaminsky discovered a fundamental flaw in theDomain Name System (DNS) protocol that could allow attackers to easily performcache poisoning attacks on mostnameservers[11][12] (djbdns,PowerDNS,MaraDNS,Secure64 andUnbound were not vulnerable).[13][14][15][16] With most Internet-based applications depending on DNS to locate their peers, a wide range of attacks became feasible, including website impersonation, email interception, and authentication bypass via the "Forgot My Password" feature on many popular websites.[17][18] After discovering the problem, Kaminsky initially contactedPaul Vixie, who described the severity of the issue as meaning "everything in the digital universe was going to have to get patched." Kaminsky then alerted theDepartment of Homeland Security and executives at Cisco andMicrosoft to work on a fix.[1]
Kaminsky worked with DNS vendors in secret to develop a patch to make exploiting the vulnerability more difficult, releasing it on July 8, 2008.[19]
Kaminsky had intended not to publicize details of the attack until 30 days after the release of the patch, but details were leaked on July 21, 2008.[20] The information was quickly pulled down, but not before it had beenmirrored by others.[21] He later presented his findings at the Black Hat Briefings, at which he wore both a suit and rollerskates.[1]
Kaminsky received a substantial amount of mainstream press after disclosing this vulnerability,[22] but experienced some backlash from the computer security community for not immediately disclosing his attack.[23] When a reporter asked him why he had not used the DNS flaw for his own financial benefit, Kaminsky responded that he felt it would be morally wrong, and he did not wish for his mother to visit him in prison.[1]
The actual vulnerability was related to DNS only having 65,536 possible transaction IDs, a number small enough to simply guess given enough opportunities.Dan Bernstein, author of djbdns, had reported this as early as 1999.[24] djbdns dealt with the issue using Source Port Randomization, in which the UDP port was used as a second transaction identifier, thus raising the possible ID count into the billions. Other more popular name server implementations left the issue unresolved due to concerns about performance and stability, as many operating system kernels simply weren't designed to cycle through thousands ofnetwork sockets a second. Instead, other implementers assumed that DNS'stime to live (TTL) field would limit a guesser to only a few attempts a day.[25]
Kaminsky's attack bypassed this TTL defense by targeting "sibling" names like "83.example.com" instead of "www.example.com" directly. Because the name was unique, it had no entry in the cache, and thus no TTL. But because the name was a sibling, the transaction-ID guessing spoofed response could not only include information for itself, but for the target as well. By using many "sibling" names in a row, he could induce a DNS server to make many requests at once. This tactic provided enough opportunities to guess the transaction ID to successfully spoof a reply in a reasonable amount of time.[26]
To fix this issue, all major DNS servers implemented Source Port Randomization, as djbdns and PowerDNS had done before. This fix makes the attack up to 65,536 times harder. An attacker willing to send billions of packets can still corrupt names.[24]DNSSEC, which Kaminsky spoke in favor of, has since been widely (but not universally) deployed, bringing cryptographic assurance to results provided by DNS.[27]
On March 27, 2009, Kaminsky discovered thatConficker-infected hosts have a detectable signature when scanned remotely.[28] Signature updates for a number of network scanning applications are now available, includingNMap[29] andNessus.[30]
In 2009, in cooperation withMeredith L. Patterson andLen Sassaman, Kaminsky discovered numerous flaws in theSSL protocol. These include the use of the weakMD2 hash function byVerisign in one of their root certificates and errors in the certificate parsers in a number of Web browsers that allow attackers to successfully request certificates for sites they do not control.[31][32]
On July 28, 2009, Kaminsky, along with several other high-profile security consultants, experienced the publication of their personal email and server data by hackers associated with the "Zero for 0wned" online magazine.[33][34][35] The attack appeared to be designed to coincide with Kaminsky's appearance at the Black Hat Briefings.[36]
In June 2010, Kaminsky released Interpolique,[37][38] a beta framework for addressing injection attacks such asSQL injection andcross-site scripting in a manner comfortable to developers.[39]
The New York Times wrote that "in a community known for its biting, sometimesmisogynistic discourse onTwitter, Mr. Kaminsky stood out for his empathy." He was known for regularly paying for hotels or travel bills for other people going to Black Hat, and once paid for a plane ticket for a friend of his after she had broken up with her boyfriend; the pair later married. At various points in his career, Kaminsky shifted his focus to work on projects related to his friends' and family's health, developing an app that helpscolorblind people, working onhearing aid technology, and developingtelemedicine tools related toAIDS among refugees forAcademic Model Providing Access to Healthcare (AMPATH). According to his mother, "he did things because they were the right thing to do, not because they would elicit financial gain."[1]
Kaminsky was also an outspokenprivacy rights advocate. During theFBI–Apple encryption dispute, he criticized comments by then-FBI directorJames Comey, saying "what is the policy of the United States right now? Is it to make things more secure or to make them less secure?" In a 2016 interview, Kaminsky said, "the Internet was never designed to be secure. The Internet was designed to move pictures of cats ... We didn’t think you’d be moving trillions of dollars onto this. What are we going to do? And here’s the answer: Some of us got to go out and fix it."[1]
Kaminsky died on April 23, 2021, ofdiabetic ketoacidosis at his home in San Francisco.[40][41] He had been frequently hospitalized for the disease in prior years. After his death, he received tributes from theElectronic Frontier Foundation, which called him a "friend of freedom and embodiment of the true hacker spirit", and fromJeff Moss, who said Kaminsky should be in theInternet Hall of Fame.[1] On December 14, 2021, that wish came to fruition.[42]
"We worked with vendors on a coordinated patch," said Kaminsky, noting this is the first time such a coordinated multi-vendor synchronized patch release has ever been carried out. Microsoft, Sun, ISC's DNS Bind, and Cisco have readied DNS patches, said Kamisnky. "The patch was selected to be as non-disruptive as possible." ... Lack of an applied patch in the ISP infrastructure would mean "they could go after your ISP or Google and re-direct them pretty much wherever they wanted." Both current and older versions of DNS may be vulnerable, Kaminsky says, and patches may not be available for older DNS software. He says Yahoo was vulnerable because it uses an older version of BIND but had committed to upgrading to BIND 9.0.
The cybersecurity world woke up Saturday to news of the sudden passing of Dan Kaminsky, a celebrated hacker who is widely credited with pioneering research work on DNS security.