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.

Risk

3/1/2010
10:29 AM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

App Insecurity: More Than Half Fail Security Tests First Time

Applications are where the action is, both for business productivity and, not at all coincidentally, for exploits. A new report from Veracode charges that 58% of reviewed apps flunked security tests the first time.

Applications are where the action is, both for business productivity and, not at all coincidentally, for exploits. A new report from Veracode charges that 58% of reviewed apps flunked security tests the first time.The Veracode State of Software Security report, (free download, registration required) might just take your breath away: 58% of the apps submitted for Veracode security testing and review contained exploitable vulnerabilities.

What's most breathtaking about this, from my perspective, is that these apps -- 1,600 of 'em, both commercial software and internally developed programs, including open source -- was the the fact that they were submitted to Veracode's security tests. The developers clearly felt confident that they'd covered their security bases.

Just as clearly, the confidence was misplaced.

According to Veracode's report, the most common vulnerability was susceptibility to Cross-Site Scripting (XSS) attacks.

The damning thing about the prevalence of persistent XSS and other common and well-known and well understood vulnerabilities is made clear in the report's blunt words:

"The pervasiveness of easily remedied vulnerabilities indicates a lack of developer education on secure coding."

Open source apps came off better than others, at least in terms of closing the security holes Veracode uncovered. While initial open source app submissions tended to suffer vulnerability levels similar to those of commercial apps, open source programs got fixed faster, as Veracode noted:

Open Source project teams remediated security vulnerabilities faster than all other users of Veracodes application risk management services platform. Open Source applications took only 36 days from first submission to reach an acceptable security score, compared to 48 days for Internally Developed applications and 82 days for Commercial applications. This is not surprising given the numerous political and organizational complexities of enterprise development efforts and the formal, customer-centric release plans of Commercial software vendors.

Customer-centrism, whatever the platform, is unavoidable, as is market-centrism and any other -ism you care to name; but Veracode's findings indicate that security-centrism had better move to the head of the list for all developers, and soon.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Commentary
What the FedEx Logo Taught Me About Cybersecurity
Matt Shea, Head of Federal @ MixMode,  6/4/2021
Edge-DRsplash-10-edge-articles
A View From Inside a Deception
Sara Peters, Senior Editor at Dark Reading,  6/2/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
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-31811
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-31812
PUBLISHED: 2021-06-12
In Apache PDFBox, a carefully crafted PDF file can trigger an infinite loop while loading the file. This issue affects Apache PDFBox version 2.0.23 and prior 2.0.x versions.
CVE-2021-32552
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-16 package apport hooks, it could expose private data to other local users.
CVE-2021-32553
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the openjdk-17 package apport hooks, it could expose private data to other local users.
CVE-2021-32554
PUBLISHED: 2021-06-12
It was discovered that read_file() in apport/hookutils.py would follow symbolic links or open FIFOs. When this function is used by the xorg package apport hooks, it could expose private data to other local users.