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

02:05 AM
Connect Directly

Antivirus, IDS/IPS Tools Can Be Used for Attacks

Little-known vulnerabilities in AV, host-based IDS/IPS can be used by attackers to bypass the tools

European researchers recently demonstrated proof-of-concept of how your antivirus and host-based IDS/IPS engines could be used against you. (See Researchers: Bugs Can Turn Security Tools Against Their Users.)

Thierry Zoller, security engineer for German security firm n.runs AG, and Sergio Alvarez, head of research at n.runs, over the last year or so have found hundreds of vulnerabilities in these security tools, some of which have been fixed by the affected vendors.

The flaws -- which are in the "parser engines" of security scanners -- either let attackers sneak malware past AV and IDS/IPS tools and into the corporate network, or read or send email from a corporate email server as well as open a backdoor on the server.

N.runs is currently testing software it has developed to resolve this parsing problem, and plans to release it as a product in the fourth quarter.

Zoller and Alvarez demonstrated their POC at last month's HackLu2007 conference in Luxembourg. Zoller says the problem is that these parser flaws cause a layered, defense-in-depth strategy to backfire on an organization.

"Companies think they are doing defense-in-depth when they really aren't. What they are doing is increasing the attack surface exponentially, by placing one AV engine after the other," he says.

The researchers say one vendor had a code-execution bug that was 10 years old. "The parsing code simply was reused with all the new versions and never scrutinized for potential problems," he says. Code reuse is part of the problem: "When we found a parsing bug, we were 100 percent sure all the vendor's product line was affected," he says.

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • n.runs AG

    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
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 5/28/2020
    Stay-at-Home Orders Coincide With Massive DNS Surge
    Robert Lemos, Contributing Writer,  5/27/2020
    Register for Dark Reading Newsletters
    White Papers
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: Can you smell me now?
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    PUBLISHED: 2020-05-29
    There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
    PUBLISHED: 2020-05-29
    A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
    PUBLISHED: 2020-05-29
    All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.