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.

Vulnerabilities / Threats

1/14/2015
10:30 AM
Giora Engel
Giora Engel
Commentary
Connect Directly
Facebook
Twitter
LinkedIn
Google+
RSS
E-Mail vvv
100%
0%

4 Mega-Vulnerabilities Hiding in Plain Sight

How four recently discovered, high-impact vulnerabilities provided "god mode" access to 90% of the Internet for 15 years, and what that means for the future.

The Kerberos Checksum Vulnerability disclosed last month was just the latest in a string of massive vulnerabilities that were discovered over the course of only eight months last year. Did I say massive? More like earth-shattering, and potentially destructive (in computer terms) on a Biblical scale. Not for nothing have we taken to referring to them as the Four Horsemen of the Apocalypse. Although they may not be heralding the actual Judgment Day, these four vulnerabilities should serve as a wakeup call to anyone even remotely concerned about information security.

The four were disclosed between April and November of last year. Individually, each was referred to as a “black swan event,” or a “unicorn.” We question this attempt to emphasize the rarity and unpredictability of such vulnerabilities. Four in less than a year? This would seem like a flock of black swans or a herd of unicorns. What if these types of potentially devastating flaws are not as rare as we thought? What if these four, as with the actual horsemen, are the harbingers of far, far worse?

By way of reminder, the four vulnerabilities, in order of disclosure, are:
●   Heartbleed (CVE-2014-0160)
●   Shellshock (CVE-2014-6271 and CVE-2014-7169)
●   Winshock (CVE-2014-6332) (aka “Windows OLE Automation Array Remote Code Execution Vulnerability”)
●   Kerberos Checksum Vulnerability (CVE-2014-6324)

Why are these four so significant? Let’s take a look at what makes them stand out.

Wildly massive scope
If it has a processor and is connected to the Internet, one of these four can (and probably did) directly and significantly affect it:
●   Heartbleed. Impacts encrypted Web communications to over 66 % of Web servers
●   Shellshock. Impacts any UNIX/Linux server
●   Winshock. Impacts any Windows workstation
●   Kerberos Checksum. Impacts any Windows-based managed network

This means that a hacker with prior knowledge of these vulnerabilities could easily:
●     Gain access to any Web server’s private certificate and use it to eavesdrop on encrypted Web traffic or perform man-in-the-middle (MITM) attacks
●     Perform remote code execution (meaning “do whatever he or she wants”) on any UNIX/Linux internet servers
●     Run any code with the highest privileges on any Windows workstation just by having it surf to a specially crafted Web page (a.k.a. a “drive-by attack”)
●     Gain unlimited (“domain admin”) privileges over managed corporate networks (which represent over 90% of corporate networks today)

Unbelievable age
Unlike malware or various recently-damaging and sophisticated cyberattacks, which were created and discovered in the modern era, some of these vulnerabilities have been around since many security admins were in diapers.
●     Shellshock: existent for 25 years
●     Winshock: existent for 19 years
●     Kerberos Checksum Vulnerability: existent for 14 years
●     Heartbleed: existent for “only” two years

This means that these high-impact vulnerabilities remained unnoticed and were hiding in plain sight for an average of 15 years. Even with all the super-talented security researchers looking for weaknesses, performing code reviews and more, these vulnerabilities continued to provide “god mode” access to 90% of the Internet.

Covering all sources
Our four vulnerabilities equally covered open and closed source systems -- none were immune:
●     Heartbleed -- open source
●     Shellshock -- open source
●     Winshock - -closed source
●     Kerberos Checksum -- closed source

What else is lurking
Companies should initiate targeted efforts to expose and mitigate the hidden breaches that lurk in their networks, especially since we now know that some of the core IT system infrastructure that we’ve trusted and used for decades is vulnerable. Security experts everywhere should understand that the (figurative) apocalypse is already upon us. Our networks are already breached.

Security practitioners also need to pursue attackers actively and continuously throughout the internal network in order to find those that have circumvented traditional threat prevention systems by exploiting the unknown vulnerabilities like those listed above. We need to identify the behavior of these attackers as early as possible by identifying the subtle changes in user behavior that can indicate malicious attack behavior. Then, even if attackers are able to find these vulnerabilities, we can minimize or even eliminate the potential damage if we find them early in the attack lifecycle. That should be the goal in this new reality that we live in.

Giora Engel, vice president, product & strategy at LightCyber is a serial entrepreneur with many years of technological and managerial experience. For nearly a decade, he served as an officer in an elite technological unit in the Israel Defense Forces, where he initiated and ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
1/16/2015 | 8:56:21 AM
Incident Response
This article points out great points as to why an efficient Incident Response Team is imperative to have in the enterprise. With multi-department involvement the organization can quickly plan and mitigate the threat if it applies to them. Without one you leave your organization at risk for years to come. I would imagine that the 4 unicorns are still prevalent in a majority of enterprises due to lack of a formidable incident response team.
Stop Defending Everything
Kevin Kurzawa, Senior Information Security Auditor,  2/12/2020
Small Business Security: 5 Tips on How and Where to Start
Mike Puglia, Chief Strategy Officer at Kaseya,  2/13/2020
5 Common Errors That Allow Attackers to Go Undetected
Matt Middleton-Leal, General Manager and Chief Security Strategist, Netwrix,  2/12/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
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
How Enterprises Are Developing and Maintaining Secure Applications
How Enterprises Are Developing and Maintaining Secure Applications
The concept of application security is well known, but application security testing and remediation processes remain unbalanced. Most organizations are confident in their approach to AppSec, although others seem to have no approach at all. 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-2019-5613
PUBLISHED: 2020-02-18
In FreeBSD 12.0-RELEASE before 12.0-RELEASE-p13, a missing check in the ipsec packet processor allows reinjection of an old packet to be accepted by the ipsec endpoint. Depending on the higher-level protocol in use over ipsec, this could allow an action to be repeated.
CVE-2020-7450
PUBLISHED: 2020-02-18
In FreeBSD 12.1-STABLE before r357213, 12.1-RELEASE before 12.1-RELEASE-p2, 12.0-RELEASE before 12.0-RELEASE-p13, 11.3-STABLE before r357214, and 11.3-RELEASE before 11.3-RELEASE-p6, URL handling in libfetch with URLs containing username and/or password components is vulnerable to a heap buffer over...
CVE-2019-10792
PUBLISHED: 2020-02-18
bodymen before 1.1.1 is vulnerable to Prototype Pollution. The handler function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10793
PUBLISHED: 2020-02-18
dot-object before 2.1.3 is vulnerable to Prototype Pollution. The set function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.
CVE-2019-10794
PUBLISHED: 2020-02-18
All versions of component-flatten are vulnerable to Prototype Pollution. The a function could be tricked into adding or modifying properties of Object.prototype using a __proto__ payload.