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.

Perimeter

7/16/2007
08:38 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Black Hat: DLP Hack

Researchers will show how some data leakage prevention products are buggy - and even risky

Careful -- your data leak prevention tools may be, well, leaky.

A pair of researchers has discovered multiple types of flaws in various vendors' DLP products that would let an attacker evade them, alter their records of stolen data, and even use them to bot-infect client machines.

At the heart of the problem is the way some DLP products are being designed, the researchers say. Their underlying approach, a sort of honor system, is problematic: "It's like handing a bracelet to all the suspects and saying, 'don't do anything wrong, or we'll catch you,'" says Eric Mondi, a security researcher with Matasano Security who led the firm's research on DLP products, which will be presented at Black Hat USA next month in Las Vegas.

"By the time you've detected your most sensitive information was leaked, the ultimate value of the DLP product is [gone]" and the attacker has copied a dossier of data on your firm's Social Security numbers, says Thomas Ptacek, co-founder and researcher with Matasano Security. "Forget about calling the security team in: It's over. You need to call PR and try to mitigate" the publicity fallout, he says.

Matasano won't name names, but several of the DLP vendors the firm alerted about the bugs -- which include buffer overflows and SQL injection -- are already working on fixes. Even so, enterprises need to know that these tools can backfire if they're not secured or audited, the researchers say.

"DLP is a top line-item for IT," Ptacek says. "A vulnerability in the piece of software that controls hundreds or thousands of machines is a catastrophe... if an attacker can find that vulnerability and take control of it. If it’s not extremely well-audited, there [will be] latent botnet infections on your network."

Some DLP products are especially leaky. The communication between agent and server was weak in many DLP products the researchers tested. "It was mainly ad hoc and weak encryption," notes Ptacek. "This data is the crown jewels of the enterprise, and the communication between agent and server has to be [better] protected."

And with Windows machines, DLP products must embed code into the kernel, which of course opens another can of worms. "The [more] stuff that's loaded into the kernel, the harder it [the DLP product] is to evade," Ptacek says. "But it also exposes more vulnerabilities to the kernel itself."

Monti says he and Ptacek will demonstrate at Black Hat a fictional DLP product that basically combines typical DLP features (in addition to the common bugs) to illustrate the risks of these tools. The goal of the researchers is to make organizations aware of these vulnerabilities in DLP products, and to know how to spot them.

"One of the things we advocate is that they do their homework on all regulatory compliance criteria," Monti says. "If they are using DLP products that don't comply to that level... they are actually failing compliance, because they are using this security product," Monti notes.

Cory Scott, vice president of global research, guidance, and consulting at ABN-AMRO, says security tools shouldn't introduce any risk to the enterprise. "The technology is only as good as the implementation," says Scott, who was speaking independently, not on behalf of ABN-AMRO. "In the cases of the vendors that Tom and company looked at, it appears as if the development and design practices were lacking. Think of the Hippocratic oath: You don't want the cure to be worse than the disease."

Still, although these products won't stop a determined attacker, Scott says, if you properly vet and audit them, you're practicing due diligence in protecting your data as well as that of your customers.

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • Black Hat Inc.
  • Matasano Security LLC 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

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    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-11498
    PUBLISHED: 2020-04-02
    Slack Nebula through 1.1.0 contains a relative path vulnerability that allows a low-privileged attacker to execute code in the context of the root user via tun_darwin.go or tun_windows.go. A user can also use Nebula to execute arbitrary code in the user's own context, e.g., for user-level persistenc...
    CVE-2020-11499
    PUBLISHED: 2020-04-02
    Firmware Analysis and Comparison Tool (FACT) 3 has Stored XSS when updating analysis details via a localhost web request, as demonstrated by mishandling of the tags and version fields in helperFunctions/mongo_task_conversion.py.
    CVE-2020-7628
    PUBLISHED: 2020-04-02
    install-package through 1.1.6 is vulnerable to Command Injection. It allows execution of arbitrary commands via the device function.
    CVE-2020-7629
    PUBLISHED: 2020-04-02
    install-package through 0.4.0 is vulnerable to Command Injection. It allows execution of arbitrary commands via the options argument.
    CVE-2020-7630
    PUBLISHED: 2020-04-02
    git-add-remote through 1.0.0 is vulnerable to Command Injection. It allows execution of arbitrary commands via the name argument.