Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

4/10/2014
02:20 PM
Marilyn Cohodas
Marilyn Cohodas
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Flash Poll: Broken Heartbeat

What steps do you plan to take in response to the Heartbleed bug? Take our poll and share your reasons in the comments.

If your website hasn’t been broken by the now infamous Heartbleed bug (and it probably hasn’t) that doesn’t mean you’re out of danger either as a member of an enterprise security team or as an end-user banking, shopping, or just plain surfing online.

Considered one of the biggest Internet security events ever (security guru Bruce Schneier ranks it 11 on a scale of 1-10),  the flaw has been quietly existing out in the wild for two years. Now, after the widespread publicity this week, experts predict it will become an even more popular attack vector, exposing millions of passwords and personal information, including credit-card numbers, email accounts, and a wide range of online commerce.

The implications for organizations are serious -- and ongoing. As Bishop Fox security analyst Tim Sapio observes in Heartbleed: Examining The Impact, "One thing is certain: If you do not take measures now against this bug, you will be hacked sooner rather than later. The attack is simply too easy to perform."

In his blog, Sapio offers prescriptive advice and resources about how to patch the flawed "Heartbeat" function of TLS, or filter out Heartbeat requests before they reach vulnerable devices. But as you consider and deploy options, we hope you will share your plans and concerns with other members of the Dark Reading community by participating in our flash poll: Broken Heartbeat.

Here’s our question: What steps do you plan to take in response to the Heartbleed bug? You can check all of the responses that apply, and, if we’ve missed a tactic you’re considering, you can tell us in the comments. We also hope you’ll use this poll as a forum to discuss ongoing issues as implications of the bug become clearer over time. For now, your responses to the poll include:

  • We have installed, or are in the process of installing, the OpenSSL Heartbeat update/fix
  • We’re replacing digital certificates
  • We’re forcing end-users to change passwords
  • We’re not doing anything; costs too much
  • What’s the Heartbleed bug?
  • Other (Please explain in the comments)

Click here to take the poll, then let’s chat about it in the comments.

Marilyn has been covering technology for business, government, and consumer audiences for over 20 years. Prior to joining UBM, Marilyn worked for nine years as editorial director at TechTarget Inc., where she launched six Websites for IT managers and administrators supporting ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-22861
PUBLISHED: 2021-03-03
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted ...
CVE-2021-22862
PUBLISHED: 2021-03-03
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with the ability to fork a repository to disclose Actions secrets for the parent repository of the fork. This vulnerability existed due to a flaw that allowed the base reference of ...
CVE-2021-22863
PUBLISHED: 2021-03-03
An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would b...
CVE-2020-10519
PUBLISHED: 2021-03-03
A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the Gi...
CVE-2021-21353
PUBLISHED: 2021-03-03
Pug is an npm package which is a high-performance template engine. In pug before version 3.0.1, if a remote attacker was able to control the `pretty` option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was p...