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

2/5/2015
10:00 AM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Scan Finds 'Ghost' Haunting Critical Business Applications

Some 41% of enterprise applications using GNU C Library (glibc) employ the Ghost-ridden 'gethostbyname' function, Veracode discovers.

Ghost is alive and well in many critical business applications, suggesting the vulnerability may be more pervasive than originally thought, new data shows.

Application security vendor Veracode found in its cloud-based scanning service that 41% of its customers' enterprise applications that use the GNU C library, aka glibc, call the Ghost-ridden gethostbyname function.

Ghost--CVE-2015-0235--is a serious buffer overflow vulnerability affecting various Linux systems. The flaw in Linux's glibc could allow an attacker to remotely wrest control of a system without authenticating to it to insert malware, or to wage distributed denial-of-service attacks, for instance. It's found in various Linux appliances and affects Debian 7, Red Hat Enterprise Linux 6 and 7, CentOS 6 and 7, and Ubuntu 12.04, as well as other Linux implementations. Glibc versions 2.2 through 2.17 are vulnerable to Ghost. All of the known affected Linux systems now have patches available.

Veracode says some 80% of those applications it analyzed using glibc were rated as highly business-critical by the organizations, which indicates they may be financial transaction applications or others that access sensitive databases.

"The pervasiveness [of Ghost, we found] was kind of surprising," says Chris Wysopal, CTO of Veracode. When the bug was first revealed last month by Qualys, the good news was that it was an "old function," so newer systems were likely safe, he says.

"But there's a lot of old software out there that is running" it, he says.

Ghost may affect more types of systems that originally thought, too:  Veracode also found that while 72% of the potentially Ghost-vulnerable applications were written in C or C++, which has been associated with Ghost, others they saw were written in Java, .NET, and PHP, programming languages.

The good news, still, is that exploiting Ghost isn't simple, as many experts have pointed out, and it's not a one-size-fits-all attack. "If you look at the way Ghost exploitation is presenting itself, it was very different in every application," Wysopal says. "It depends on how the application is using IP addresses and hostname lookups, and the way it's calling gethostbyname."

That means any Ghost attacks would most likely be targeted, and most likely be by sophisticated attackers since the bug is so implementation-dependent. "This [type of attacker] will fingerprint the software you have exposed on a desktop or on the Net, and get that software and check it out and [see] if it's vulnerable," he says.

Wolfgang Kandek, CTO at Qualys, recently told Dark Reading that while exploitable prospects aren't necessarily easy to find, there were indeed likely others out there. "Ghost has multiple remote vectors, [and] we only know of one so far," he says, referring to the Ghost proof-of-concept his team demonstrated exploiting the Exim mail server.

Veracode's advice: keep all Internet-facing systems at the latest patch level. "Don't try to figure out if you're vulnerable or not. Just patch," Wysopal says. As for Linux-based appliances and other embedded devices that may not get patches, or systems behind your firewall, it won't be so simple. "They might not be as easy to patch," he says.

Ghost is the latest in a string of big open-source software bugs that have been disclosed over the past year or so. It won't be the last, either, according to Wysopal, since there are so many open-source components being used today in software.

"We're going to see more of the more critical vulnerabilities. This is definitely not going away," he says. "Know what components you're using in your organization, and applications you're writing or building, and track them so you're ready to respond when a vulnerability becomes public." 

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
2/5/2015 | 12:02:16 PM
Validation Scans
It is imperative to make sure that after patching is performed for Ghost that validation scans are performed to ensure that the vulnerability no longer exists. I know the patch requires a reboot and there is always the possibility of an issue during patching. Always ensure the patch was applied correctly through validation scans.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
2/5/2015 | 12:32:25 PM
Re: Validation Scans
@RyanSepe, that is great advice. Patching isn't just apply-it-and-forget it, especially with tricky bugs like these.
Commentary
How SolarWinds Busted Up Our Assumptions About Code Signing
Dr. Jethro Beekman, Technical Director,  3/3/2021
News
'ObliqueRAT' Now Hides Behind Images on Compromised Websites
Jai Vijayan, Contributing Writer,  3/2/2021
News
Attackers Turn Struggling Software Projects Into Trojan Horses
Robert Lemos, Contributing Writer,  2/26/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: George has not accepted that the technology age has come to an end.
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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23351
PUBLISHED: 2021-03-08
The package github.com/pires/go-proxyproto before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in ...
CVE-2009-20001
PUBLISHED: 2021-03-07
An issue was discovered in MantisBT before 2.24.5. It associates a unique cookie string with each user. This string is not reset upon logout (i.e., the user session is still considered valid and active), allowing an attacker who somehow gained access to a user's cookie to login as them.
CVE-2020-28466
PUBLISHED: 2021-03-07
This affects all versions of package github.com/nats-io/nats-server/server. Untrusted accounts are able to crash the server using configs that represent a service export/import cycles. Disclaimer from the maintainers: Running a NATS service which is exposed to untrusted users presents a heightened r...
CVE-2021-27364
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. drivers/scsi/scsi_transport_iscsi.c is adversely affected by the ability of an unprivileged user to craft Netlink messages.
CVE-2021-27365
PUBLISHED: 2021-03-07
An issue was discovered in the Linux kernel through 5.11.3. Certain iSCSI data structures do not have appropriate length constraints or checks, and can exceed the PAGE_SIZE value. An unprivileged user can send a Netlink message that is associated with iSCSI, and has a length up to the maximum length...