Free Privileged Account Discovery Tool: Identify & secure credentials to stop lateral movement. Download Free

BeyondTrust
  • Products
    Privileged Password Management
    Discover, manage, audit, and monitor privileged accounts
    Password Safe DevOps Secrets Safe
    Endpoint Privilege Management
    Manage privileges on Windows, Mac, Linux, and Unix endpoints
    Windows and Mac Unix and Linux Active Directory Bridge
    Secure Remote Access
    Centrally manage and secure remote access for service desks and vendors
    Remote Support Privileged Remote Access
    BeyondInsight Analytics
    See All Solutions
  • Resources

    Universal Privilege Management

    Our innovative Universal Privilege Management approach secures every user, asset, and session across your entire enterprise.

    Watch Video

    Learn

    Case Studies
    Competitor Comparisons
    Datasheets
    Glossary
    Product Demos
    Whitepapers

    Attend

    Events
    Go Beyond
    Training
    Webinars

    Support

    Changelog
    Professional Services
    Technical Documentation
  • Blog
  • Partners
  • Contact
  • Support
  • Services
  • Training
  • Events
  • Company

Shellshock: What you need to know

October 20, 2017

  • Blog
  • Archive

The InfoSec community has gone into overdrive in the last few days dealing with the 'Shellshock' bug. There is good reason for this, millions of systems around the globe are vulnerable to this bug which lets attackers run code on that system.

So what is Shellshock?

Shellshock or CVE 2014-6271 is an incredibly simple bug that requires no advanced code or sophisticated setup. In truth, it’s astonishing that it has taken so long to surface.

The bug is in Bash (Bourne Again Shell) the command interpreter used in Linux, Unix and OSX operating systems. It exploits the fact that Bash executes any code that is tagged onto the end of a function without validation. This allows attackers to disclose data and run commands on a target system.

Why is it such a big problem?

The reason the problem is so wide spread is that Bash is widely installed on a range of devices such as routers, industrial control systems and servers. The main concern at the moment is systems that are directly connected to the internet can be exploited remotely by attackers. Shodan has already shown that a huge number of critical systems and industrial controls are connected directly to the internet and are potentially vulnerable.

Internal systems also need to be patched as they present a target to attackers who manage to infiltrate the network. Many embedded devices such as VoIP phones and network printers will prove a significant challenge as manufacturers are slow to issue updates for older equipment. This was proven after Heartbleed where a significant number of devices never received an update.

What to do?

Businesses should identify and patch vulnerable systems as soon as possible as thousands of attacks are already targeting this bug. The good news is that despite the wide spread use of Bash not all systems are externally vulnerable. The most common problem areas are Apache web servers using mod_cgi, mod_cgid or Git over SSH. Although OSX does contain the bug it is safe by default unless users have configured the advanced UNIX services.

The key to success is being able to rapidly identify vulnerable systems and either patch or take them offline. External and cloud service providers are being generally proactive in warning users of issues and taking steps to resolve them. With the internet awash with these attacks it is best to take immediate action especially with business critical systems.

The technical summary

The issue is in the way in which Bash handles functions, it looks at the command and identifies the function definition using " (){ " characters. It then evaluates and executes this definition using the parse_and_execute() function. So if we add some extra commands after the function definition these should also be executed.

We can test this by running the following command.

myTest=’(){;}; echo “This is bad"’ bash -c "echo This is OK"

If we run this command on a vulnerable host it will print "This is bad" if it does not print this and just prints "This is OK" then the system is not vulnerable.

James Maude

Stay Up To Date

Get the latest news, ideas, and tactics from BeyondTrust. You may unsubscribe at any time.

I agree to receive product related communications from BeyondTrust as detailed in the Privacy Policy, and I may manage my preferences or withdraw my consent at any time.

You May Also Be Interested In:

Webcasts | February 09, 2021

Customer Webinar: Remote Support 21.1 Released!

Webcasts | February 24, 2021

Your PAM 2021 Blueprint: Securing Privileged Accounts for On-Premises and Cloud Assets

Whitepapers

Evolving Privileged Identity Management (PIM) In The 'Next Normal'

BeyondTrust Logo
  • Facebook
  • Twitter
  • LinkedIn

Keep up with BeyondTrust

I agree to receive product related communications from BeyondTrust as detailed in the Privacy Policy, and I may manage my preferences or withdraw my consent at any time.

Customer Support
Contact Sales

Products

  • Endpoint Privilege Management
  • Password Management
  • Privileged Remote Access
  • DevOps Secrets Safe
  • Remote Support

Resources

  • Blog
  • Case Studies
  • Competitor Comparisons
  • Datasheets
  • Glossary
  • Videos
  • Webcasts
  • Whitepapers

About

  • Company
  • Careers
  • Contact
  • Events
  • Leadership Team
  • Partner Program
  • Press

Languages

  • English
  • German
  • French
  • Spanish
  • Korean
  • Portuguese
  • Japanese
  • Privacy
  • Security
  • Manage Cookies
  • WEEE Compliance

Copyright © 1999 — 2020 BeyondTrust Corporation. All rights reserved. Other trademarks identified on this page are owned by their respective owners. BeyondTrust Corporation is not a chartered bank or trust company, or depository institution. It is not authorized to accept deposits or trust accounts and is not licensed or regulated by any state or federal banking authority.