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
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 4/7/2020
The Coronavirus & Cybersecurity: 3 Areas of Exploitation
Robert R. Ackerman Jr., Founder & Managing Director, Allegis Capital,  4/7/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
State of Cybersecurity Incident Response
State of Cybersecurity Incident Response
Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-1627
PUBLISHED: 2020-04-08
A vulnerability in Juniper Networks Junos OS on vMX and MX150 devices may allow an attacker to cause a Denial of Service (DoS) by sending specific packets requiring special processing in microcode that the flow cache can't handle, causing the riot forwarding daemon to crash. By continuously sending ...
CVE-2020-1628
PUBLISHED: 2020-04-08
Juniper Networks Junos OS uses the 128.0.0.0/2 subnet for internal communications between the RE and PFEs. It was discovered that packets utilizing these IP addresses may egress an EX4300 switch, leaking configuration information such as heartbeats, kernel versions, etc. out to the Internet, leading...
CVE-2020-1629
PUBLISHED: 2020-04-08
A race condition vulnerability on Juniper Network Junos OS devices may cause the routing protocol daemon (RPD) process to crash and restart while processing a BGP NOTIFICATION message. This issue affects Juniper Networks Junos OS: 16.1 versions prior to 16.1R7-S6; 16.2 versions prior to 16.2R2-S11; ...
CVE-2020-1630
PUBLISHED: 2020-04-08
A privilege escalation vulnerability in Juniper Networks Junos OS devices configured with dual Routing Engines (RE), Virtual Chassis (VC) or high-availability cluster may allow a local authenticated low-privileged user with access to the shell to perform unauthorized configuration modification. This...
CVE-2020-1634
PUBLISHED: 2020-04-08
On High-End SRX Series devices, in specific configurations and when specific networking events or operator actions occur, an SPC receiving genuine multicast traffic may core. Subsequently, all FPCs in a chassis may reset causing a Denial of Service. This issue affects both IPv4 and IPv6. This issue ...