Attacks/Breaches

7/19/2017
01:30 PM
Kelly Sheridan
Kelly Sheridan
Slideshows
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Best of Black Hat: 20 Epic Talks in 20 Years

In celebration of Black Hat's 20th birthday, we take a look back at the most memorable presentations and demos since the show's inception in 1997.
Previous
1 of 21
Next

(Image: Black Hat)

(Image: Black Hat)

This year marks the 20th anniversary of Black Hat, the information security conference founded by Jeff Moss in 1997. What began as a single meetup in Las Vegas has expanded around the world to host events in the United States, Europe, and Asia.

Over the years, Black Hat has brought together CISOs, researchers, academics, IT specialists, analysts, federal employees, cryptographers, and many other security professionals to learn about, and discuss, the threats and trends shaping their industry.

Much of the learning takes place in the Black Hat Briefings, which were created to give security pros a place to discover new threats and developments that could potentially put them at risk. Each year, researchers take the conference stage to share their latest work and exploits.

Twenty years is a long time in an industry where threats change by the minute. The many vulnerabilities exposed at Black Hat have affected everything from consumer devices to critical infrastructure.

For example, anyone who was at Black Hat 2010 recalls when the late Barnaby Jack, then director of research at IOActive, demonstrated how a cybercriminal could compromise an ATM and steal cash, copy customers' card data, or learn the machines' master passwords.

Information released at Black Hat has proven groundbreaking and game-changing for those in attendance. Here, we take a look back at the "best of" Black Hat talks, discoveries, and moments over the past 20 years.

Do you have a favorite Black Hat moment that didn't make this list? If so, we'd love to hear about it! Feel free to share your thoughts in the comments.  

 

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Previous
1 of 21
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
What We Talk About When We Talk About Risk
Jack Jones, Chairman, FAIR Institute,  7/11/2018
Ticketmaster Breach Part of Massive Payment Card Hacking Campaign
Jai Vijayan, Freelance writer,  7/10/2018
7 Ways to Keep DNS Safe
Curtis Franklin Jr., Senior Editor at Dark Reading,  7/10/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Locked device, Ha! I knew there was another way in.
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14337
PUBLISHED: 2018-07-17
The CHECK macro in mrbgems/mruby-sprintf/src/sprintf.c in mruby 1.4.1 contains a signed integer overflow, possibly leading to out-of-bounds memory access because the mrb_str_resize function in string.c does not check for a negative length.
CVE-2018-14329
PUBLISHED: 2018-07-17
In HTSlib 1.8, a race condition in cram/cram_io.c might allow local users to overwrite arbitrary files via a symlink attack.
CVE-2018-14331
PUBLISHED: 2018-07-17
An issue was discovered in XiaoCms X1 v20140305. There is a CSRF vulnerability to change the administrator account password via admin/index.php?c=index&a=my.
CVE-2018-14333
PUBLISHED: 2018-07-17
TeamViewer through 13.1.1548 stores a password in Unicode format within TeamViewer.exe process memory between "[00 88] and "[00 00 00]" delimiters, which might make it easier for attackers to obtain sensitive information by leveraging an unattended workstation on which TeamViewer has ...
CVE-2018-14334
PUBLISHED: 2018-07-17
manager/editor/upload.php in joyplus-cms 1.6.0 allows arbitrary file upload because detection of a prohibited file extension simply sets the $errm value, and does not otherwise alter the flow of control. Consequently, one can upload and execute a .php file, a similar issue to CVE-2018-8766.