Vulnerabilities / Threats
7/30/2014
11:10 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Security Holes Found In Some DLP Products

Researchers to reveal key security flaws in commercial and open-source data loss prevention software at Black Hat USA next week.

It's a case of a security tool harboring security vulnerabilities: A pair of researchers has discovered multiple flaws in commercial and open-source data loss prevention (DLP) products.

Zach Lanier, senior security researcher at Duo Security, and Kelly Lum, security engineer with Tumblr, next week at Black Hat USA in Las Vegas will demonstrate the cross-site scripting (XSS) and cross-site request forgery (CSRF) vulnerabilities they discovered in four commercial DLP products and one open-source tool they investigated. They plan to name names next week during their talk, "Stay Out of the Kitchen: A DLP Security Bake-Off," where they also will provide proof-of-concept attack examples.

Lanier and Lum -- who won't divulge full details until their talk next week -- say they really weren't surprised to find flaws in DLP systems that enterprises rely on to keep private and sensitive information from leaking outside the organization. "It was not a huge shock," Lum says. "But I was a little surprised that some of the vulnerabilities were very simple, which means they should be easily fixed. It's curious that they could have been easily avoided in the first place."

Many of the flaws were found in the web-based interfaces of the products, namely, the administrative panels. XSS and CSRF were the most common ones found there, they say.

"Some were endpoint and some were network-based… and some in how they do reporting," for example, says Lanier. "We also evaluated the document parsing pieces that classify and protect the data."

While Lanier and Lum did not find any specific bypass vulnerabilities in the DLP tools they tested, they did find flaws that would allow an attacker to reconfigure or change the behavior of the DLP system so that it no longer monitors data leaks, for example.

An attacker could shut down or reconfigure a DLP system via some of the bugs, Lanier says. "They could disable DLP policies and add new elements to the policies… or add new users."

Another scary option is that an attacker could take a document out of quarantine and siphon its contents,  he says.

"One of the DLP solutions used a Python scripting language to do a lot of the heavy lifting around the analysis engine and policy. There is an insecure module inside Python that could lead to arbitrary code execution," Lanier says. That would allow someone with access to the administrative server to spread malware to various endpoints that were managed by that server.

"Since all DLP processes run in privileged mode, they also [would allow] privileged [user] code execution. That was one of the big, non-web things we found" vulnerable, he says.

The researchers, as of this posting, were also still studying the third-party KeyView document parsing/filtering engine used by many DLP and big-data products. Lanier says they are looking for potential vulnerabilities as well as a possible inspection bypass issue, but nothing's concrete just yet.

Meanwhile, Lanier and Lum say their research shows that DLP vendors aren't properly vetting their software for flaws.

"This speaks to how important it is to start looking at these products with a more jaundiced eye. Lots of sensitive data -- credit card numbers, social security numbers" are at risk if the tools are not solid security-wise, Lum says.

Lanier will discuss the newly found vulnerabilities in commercial and open-source DLP software in today's 1:00 p.m. ET broadcast of Dark Reading Radio, "Data Loss Prevention (DLP) FAIL." Register here to tune in and ask him questions via the online chat.

Kelly Jackson Higgins is Executive Editor at DarkReading.com. 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

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
7/31/2014 | 12:21:33 PM
Re: Remediation
I agree. Unfortunaltely, you expect this from a 3rd party producing a product for its functionality. But when its functionality is security you would think that they would do their due diligence.
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
7/31/2014 | 11:21:50 AM
Re: Remediation
I know it's impossible to write perfect code, but I still can't wrap my head around how a security company could not be more careful with its software. Even if 3rd party code was the source of the vulns, they should be testing every single element of the platform. Some of these bugs would have been found in about 5 minutes, according to the researchers.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
7/31/2014 | 8:13:17 AM
Remediation
I hope that when names are dropped, vendors really take the time to close the gaps in their software. Being allowed to reconfigure policies to your will is bad enough, but being able to execute malicious code under a privileged account is even worse. I will be interested to hear if these vulnerabilities are prevalent on a 3 tier system or are more likely to happen when organizations combine the tiers.
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-0547
Published: 2015-07-04
The D2CenterstageService.getComments service method in EMC Documentum D2 4.1 and 4.2 before 4.2 P16 and 4.5 before P03 allows remote authenticated users to conduct Documentum Query Language (DQL) injection attacks and bypass intended read-access restrictions via unspecified vectors.

CVE-2015-0548
Published: 2015-07-04
The D2DownloadService.getDownloadUrls service method in EMC Documentum D2 4.1 and 4.2 before 4.2 P16 and 4.5 before P03 allows remote authenticated users to conduct Documentum Query Language (DQL) injection attacks and bypass intended read-access restrictions via unspecified vectors.

CVE-2015-0551
Published: 2015-07-04
Multiple cross-site scripting (XSS) vulnerabilities in EMC Documentum WebTop 6.7SP1 before P31, 6.7SP2 before P23, and 6.8 before P01; Documentum Administrator 6.7SP1 before P31, 6.7SP2 before P23, 7.0 before P18, 7.1 before P15, and 7.2 before P01; Documentum Digital Assets Manager 6.5SP6 before P2...

CVE-2015-1966
Published: 2015-07-04
Multiple cross-site scripting (XSS) vulnerabilities in IBM Tivoli Federated Identity Manager (TFIM) 6.2.0 before FP17, 6.2.1 before FP9, and 6.2.2 before FP15, as used in Security Access Manager for Mobile and other products, allow remote attackers to inject arbitrary web script or HTML via a crafte...

CVE-2015-4196
Published: 2015-07-04
Platform Software before 4.4.5 in Cisco Unified Communications Domain Manager (CDM) 8.x has a hardcoded password for a privileged account, which allows remote attackers to obtain root access by leveraging knowledge of this password and entering it in an SSH session, aka Bug ID CSCuq45546.

Dark Reading Radio
Archived Dark Reading Radio
Marc Spitler, co-author of the Verizon DBIR will share some of the lesser-known but most intriguing tidbits from the massive report