Application Security

2018's Most Common Vulnerabilities Include Issues New and Old

The most common vulnerabilities seen last year run the gamut from cross-site scripting to issues with CMS platforms.

It's entirely 2019, but that doesn't mean it's too late to look at lists of superlatives from 2018. In one of the latest, a security firm has released its list of the top application security vulnerabilities of 2018.

WhiteHat Security put together this list of the most common web exploits used by malicious hackers in 2018, and their list contains both new vulnerabilities and "classics" that continue to haunt the waking dreams of security professionals.

Setu Kulkarni, vice president of corporate strategy at WhiteHat Security, says that the majority of the breaches on the list come from one of two "epicenters" in software development. The first is in the wide use of open-source tools, functions, and applications in projects. "Developers can use public APIs to quickly deliver application functionality that is creating or opening a new set of vulnerabilities that that customers and the industry have to deal with," he explains.

The other vulnerability epicenter, Kulkarni says, is the rapid-fire develop/deploy cycle exemplified by DevOps. "Devops, micro services, and open source are also contributing a new set or a new kind of vulnerability into the mix because developers have now more power to push code into production," he says.

The 10 top vulnerabilities include issues as new as the jQuery File Upload vulnerability (CVE-2018-9206), a Wordpress DoS attack (CVE-2018-6989), and two versions of Drupalgeddon, to malware like Magecart. There are also classic vulnerabilities like cross-site scripting still found on the list of most common vulnerabilities of 2018. 

Asked about the reasons that put a vulnerability as old as cross-site scripting on last year's list, senior WhiteHat Security researcher Mark Rogan says that schools and training programs continue to emphasize speed over security when teaching developers. And that's a shame, he points out, since cross-site scripting is relatively easy to close. "All you have to do is validate your input and encode your data. If you do that, goodbye cross-site scripting," Rogan says.

Kulkarni says that, despite vulnerabilities that are common in applications developed through a devops process, devops is absolutely the right development model for the modern world. The important thing, he says, is to make sure that devops is done right. "It's absolutely necessary to build developers and train them in schools to write more secure code, but it's also important to have security tests that are performed at the right time."

He continues, "And what's even more important is that when these tests are performed, the feedback that goes back to the developer has to be accurate and very contextual."

Related content:

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Russia Hacked Clinton's Computers Five Hours After Trump's Call
Robert Lemos, Technology Journalist/Data Researcher,  4/19/2019
Why We Need a 'Cleaner Internet'
Darren Anstee, Chief Technology Officer at Arbor Networks,  4/19/2019
55% of SMBs Would Pay Up Post-Ransomware Attack
Dark Reading Staff 4/25/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11538
PUBLISHED: 2019-04-26
In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4, 8.3RX before 8.3R7.1, 8.2RX before 8.2R12.1, and 8.1RX before 8.1R15.1, an NFS problem could allow an authenticated attacker to access the contents of arbitrary files on the affected device.
CVE-2019-11539
PUBLISHED: 2019-04-26
In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4, 8.3RX before 8.3R7.1, 8.2RX before 8.2R12.1, and 8.1RX before 8.1R15.1 and Pulse Policy Secure version 9.0RX before 9.0R3.2, 5.4RX before 5.4R7.1, 5.3RX before 5.3R12.1, 5.2RX before 5.2R12.1, and 5.1RX before 5.1R15.1, the admin web...
CVE-2019-11540
PUBLISHED: 2019-04-26
In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4 and 8.3RX before 8.3R7.1 and Pulse Policy Secure version 9.0RX before 9.0R3.2 and 5.4RX before 5.4R7.1, an unauthenticated, remote attacker can conduct a session hijacking attack.
CVE-2019-11541
PUBLISHED: 2019-04-26
In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4, 8.3RX before 8.3R7.1, and 8.2RX before 8.2R12.1, users using SAML authentication with the Reuse Existing NC (Pulse) Session option may see authentication leaks.
CVE-2019-11542
PUBLISHED: 2019-04-26
In Pulse Secure Pulse Connect Secure version 9.0RX before 9.0R3.4, 8.3RX before 8.3R7.1, 8.2RX before 8.2R12.1, and 8.1RX before 8.1R15.1 and Pulse Policy Secure version 9.0RX before 9.0R3.2, 5.4RX before 5.4R7.1, 5.3RX before 5.3R12.1, 5.2RX before 5.2R12.1, and 5.1RX before 5.1R15.1, an authentica...