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

Cross-Scripting Errors Cause Most Web App Vulnerabilities

Despite being easy to spot and fix, XSS bugs now account for more than half of all Web application vulnerabilities, reports Veracode.

How Firesheep Can Hijack Web Sessions
(click image for larger view)
Slideshow: How Firesheep Can Hijack Web Sessions

According to static application security testing vendor Veracode, cross-site scripting (XSS) errors are now responsible for more than half of all Web application vulnerabilities. Where present, such errors can be exploited by attackers to bypass many security controls and execute malicious scripts via a user's browser.

Many XSS errors could have been prevented, however, by ensuring that developers practice secure coding techniques. "We strongly believe that many XSS errors are straightforward and easy to fix, and that much can be done to greatly reduce their occurrence," said Matt Moynahan, CEO of Veracode, in a statement. "Developer and product security teams must accept greater accountability for writing better code."

Not introducing XSS errors in the first place is a relatively straightforward process, though it requires more upfront work by developers. According to the Open Web Application Security Project (OWASP), "XSS flaws occur whenever an application takes untrusted data and sends it to a Web browser without proper validation and escaping," with escaping referring to removing or blocking characters that might be used to launch an attack.

Numerous software vendors now sell security testing tools to help ensure that developers properly validate and escape their code, among other essentials. According to Gartner Group, such vendors include HP, IBM, Veracode, Armorize Technologies, Checkmarx, Coverity, GrammaTech, Koicwork, and Parasoft.

Many software-developing organizations, however, seemingly prioritize time-to-market over secure coding. As a result, even easy-to-prevent errors, such as not blocking injection attacks or XSS bugs, have become endemic. That's in spite of numerous studies which have found that remediating software bugs costs far less in the early stages of the software development lifecycle, and especially prior to code going into production.

When done early enough in the software development lifecycle, many code fixes are also relatively easy. According to Chris Eng, senior director of security research at Veracode, "We see thousands -- sometimes tens of thousands -- of XSS vulnerabilities a week. Many are those we describe as 'trivial' and can be fixed with a single line of code,"

Veracode said that the average time required to remediate an XSS bug, based on companies that used its service to scan code before and after remediating it, was 16 days.

But if required, fixes can be made in almost no time at all, as has happened in the wake of XSS exploits against Web sites such as Facebook and Twitter. "Sometimes those companies push XSS fixes to production in a matter of hours. Are their developers really that much better? Of course not. The difference is how seriously the business takes it. When they believe it's important, you can bet it gets fixed," said Eng.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/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-24376
PUBLISHED: 2021-06-21
The Autoptimize WordPress plugin before 2.7.8 attempts to delete malicious files (such as .php) form the uploaded archive via the "Import Settings" feature, after its extraction. However, the extracted folders are not checked and it is possible to upload a zip which contained a directory w...
CVE-2021-24377
PUBLISHED: 2021-06-21
The Autoptimize WordPress plugin before 2.7.8 attempts to remove potential malicious files from the extracted archive uploaded via the 'Import Settings' feature, however this is not sufficient to protect against RCE as a race condition can be achieved in between the moment the file is extracted on t...
CVE-2021-24378
PUBLISHED: 2021-06-21
The Autoptimize WordPress plugin before 2.7.8 does not check for malicious files such as .html in the archive uploaded via the 'Import Settings' feature. As a result, it is possible for a high privilege user to upload a malicious file containing JavaScript code inside an archive which will execute w...
CVE-2021-24379
PUBLISHED: 2021-06-21
The Comments Like Dislike WordPress plugin before 1.1.4 allows users to like/dislike posted comments, however does not prevent them from replaying the AJAX request to add a like. This allows any user (even unauthenticated) to add unlimited like/dislike to any comment. The plugin appears to have some...
CVE-2021-24383
PUBLISHED: 2021-06-21
The WP Google Maps WordPress plugin before 8.1.12 did not sanitise, validate of escape the Map Name when output in the Map List of the admin dashboard, leading to an authenticated Stored Cross-Site Scripting issue