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

9/10/2008
08:30 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Report: In-Depth Analysis Finds More Severe Web Flaws

Web Application Security Consortium (WASC) report suggests automated scanning alone isn't as thorough when it comes to serious bugs

A new report on Web threats released today by the Web Application Security Consortium says that in-depth manual and automated assessments found nearly 97 percent of sites carry a severe vulnerability.

“About 7.72% [of] applications had a high-severity vulnerability detected during automated scanning,” according to the WASC report. “Detailed manual and automated assessment using white and black box methods shows that probability to detect high-severity vulnerability reaches 96.85 percent."

WASC combined custom Web application vulnerability data from 32,000 Websites that had been searched for vulnerabilities using automated scanning as well as so-called white- and black-box scans, where manual and automated analysis methods are used. Booz Allen Hamilton, BT, Cenzic, dblogic.it, HP, Positive Technologies, Veracode, and WhiteHat Security all provided “sanitized” data for the report.

The pervasive cross-site request forgery (CSRF) vulnerability didn’t get a high ranking in the report (it was found in only 1.43 percent of the apps) however -- even though it’s “the most prevalent vulnerability,” according to WASC. That’s because “it is difficult to detect automatically and because a lot of experts take its existence for granted.”

As usual, the vulnerabilities most found in Web applications were cross-site scripting, information leakage, and SQL injection. XSS accounted for 41 percent of all vulnerabilities; information leakage, 32 percent; SQL injection, 9 percent; and predictable resource location flaws, 8 percent.

Security expert Jeremiah Grossman praised the report, but says to be careful not to read too much into the data. “It’s best to view reports such as these, where the true number and type of vulnerabilities is an unknown, as the best-case scenario,” blogged Grossman, CTO of WhiteHat, and a member of WASC who contributed to the report. “There are certainly inaccuracies, such as with CSRF, but at the very least this gives us something to go on.”

But that didn’t stop experts from trying to decipher what the report reveals about the state of Web security.

“Looking at the numbers, I thought SQL injection would have a bigger presence in the number of vulnerabilities and vulnerable sites. Although the statistics seem to show the number is decreasing from previous years, do not stop fighting this class of attack, and all types of injection in general!! From a threat classification perspective, client-based attacks and information disclosure (again) are the most prevalent ones,” blogged Raul Siles of the SANS Internet Storm Center.

The report also compared the testing methodologies used to identify Web vulnerabilities. The more detailed black box and white box methods better detect authorization and authentication-type vulnerabilities and logic flaws, according to the report, and these methods also are 12.5 times more likely to detect a high-risk vulnerability than an automated scanner.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

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
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
CVE-2020-11844
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.
CVE-2020-6937
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.
CVE-2020-7648
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`
CVE-2020-7650
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.
CVE-2020-7654
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.