Each year, we publish a set of statistics summarizing the vulnerabilities we find in open source web applications. Our tests form part of Netsparker’s quality assurance practices, during which we scan thousands of web applications and websites. This helps us to add to our security checks and continuously improve the scanner’s accuracy.
This blog post includes statistics based on security research conducted throughout 2017. But first, we take a look at why we care about open source applications, and the damage that can be caused for enterprises when they go wrong.
Why Do Workplaces Use Open Source Software?
The reason for the rise in popularity of open source software in the business world is financial: your enterprise is getting great software for free. Some enterprises resonate with the open source philosophy of collaboration and giving back. This helps explain why big companies like Twitter, Tumblr, Netflix and Pinterest use and advocate for open source.
Netsparker has a natural interest in the security aspect of open source software, and also a very question; since the source code of open source projects is publically available, does that make these applications more or less secure than proprietary or closed software?
What Happens When Open Source Goes Wrong?
The global average cost of a data breach in 2017 was $3.62 million. In May to July of 2017, Equifax suffered a massive cyber-security breach, with attackers accessing hundreds of millions of customers’ personal data. Although they announced this breach in September 2017, Equifax was informed in 2016 that their website was vulnerable, and was even told which vulnerabilities to check.
Hackers exploiting open source Apache Struts vulnerabilities were blamed for the Equifax breach. Although a deserialization vulnerability in the REST plugin of Apache Struts was initially blamed, an OGNL Expression Injection vulnerability in Struts was found to be the cause for the breach.
Even though a vast amount of personal data was being exposed due to the Equifax breach, a significantly higher number of users were potentially affected by another security bug in readily available open source software. ROBOT (Return Of Bleichenbacher’s Oracle Threat) is a type of attack that revives a 19-year old vulnerability. Bleichenbacher’s RSA vulnerability is still very prevalent in the Internet and aﬀected top domains like Facebook and Paypal, along with many other vendors and open source projects. In December 2017, Netsparker released a hotfix version of our web application security scanner that included ROBOT security checks.
Why Does Netsparker Care About Open Source?
One of the best ways to demonstrate the effectiveness of Netsparker web application security scanner is to test it against a wide variety of web applications used on the web. So our security researchers scan a great variety of open source web applications including: shopping carts and e-commerce solutions, social networking web applications, forums and blogs. The complexity of the testing environment increases when you consider the big number of languages used to create web applications, such as: PHP, Java, Ruby on Rails, ASP.NET, Node.JS, Python and other frameworks.
The only reason – aside from an awesome team of dedicated Security Researchers – that we are able to scan so many web applications and detect so many vulnerabilities across such a wide range, is because automation is at the heart of the Netsparker’s web application security scanning technology.
There are a couple of neat side benefits. Open source applications development teams get free security testing, empowering them to write more secure code. If you’d like to conduct your own, free, automated web application security testing, and read more about how we’re huge supporters of the open source community, see our offer of Free Online Web Security Scans For Open Source Projects.
What Did Netsparker Discover About the State of Open Source Security In 2017?
What Is The Most Prolific Vulnerability in Open Source Applications?
The most predominant vulnerability discovered in open source web applications was Reflected XSS. This accounted for almost 70% of the overall number of reported vulnerabilities. All kinds of Cross-site Scripting (XSS) vulnerabilities ranked as number seven in the OWASP Top 10 List for 2017.
How Many Web Applications Did We Scan in 2017?
- The total number of web applications we tested and scanned in 2017 was 154, an increase of over 48% from our last report
- The most popular web application frameworks or languages in which scanned apps were developed are PHP (124), .NET (14) and Java (10)
- The most popular back-end database servers used by these scanned applications were MySQL (86), Microsoft SQL Server (13)
What Were the Vulnerability Findings for 2017?
What is of most interest to us is the numbers of vulnerabilities we found in these web applications.
- The number of vulnerable web applications was 59. This is over 38% of all the web applications we tested.
- The total number of vulnerabilities Netsparker identified in these open source sites was 346.
Which Vulnerability Types Were Detected?
The web application vulnerabilities Netsparker discovered are listed in the table below.
|Vulnerability Name||Total Occurrences||Severity Level|
|Reflected Cross-site Scripting (XSS)||240||High Severity|
|Frame Injection||29||Medium Severity|
|SQL Injection||24||Critical Severity|
|Stored Cross-site Scripting (XSS)||15||High Severity|
|Blind SQL Injection||14||Critical Severity|
|Code Evaluation||6||Critical Severity|
|Cross-Site Request Forgery (CSRF)||5||Low Severity|
|Open Redirection||5||Medium Severity|
|Boolean SQL Injection||3||Critical Severity|
|Blind Cross-site Scripting (XSS)||2||High Severity|
|Cross-site Scripting (XSS) via Remote File Inclusion (RFI)||1||High Severity|
|Server Side Template Injection (SSTI)||1||High Severity|
|Document Object Model Cross-site Scripting (DOM XSS)||1||High Severity|
Around 88% of the total vulnerabilities were either of Critical or High Severity. For more information on how Netsparker defines severity levels, see Web Application Vulnerabilities Severities Explained.
How Has the State of Web Application Security Changed Since 2016?
Whereas last year SQL Injection vulnerabilities came in second place, this year Frame Injection vulnerabilities have replaced them. The top development languages, frameworks and database servers remains the same.
What Action Did the Open Source Applications Take?
If you consult our Web Application Advisories by Netsparker list, you can see that we published 32 advisories in 2017. In addition, there are 28 in pending mode. Of these 32, 28 vendors were contacted. Out of the 59 reported web applications with vulnerabilities, only six were fixed. The number of advisories with multiple vulnerabilities was three.
Would Your Open Source Project Benefit From Free Web Vulnerability Scans?
Based on our latest statistics, a randomly-selected web application may include an average of 2.25 vulnerabilities. Developers could eliminate many of these by taking security best practice into account during the SDLC.
Does your team have time to conduct penetration testing to find them all? And, do you know what to do, to remove the vulnerability, and determine whether it is gone? Would you like to have access to an automated web application security scanning solution that would detect them all – and offer remediation recommendations?
Netsparker offers Free Online Web Application Security Scans for Open Source Projects. This is our token of appreciation to all the developers in the open source community and Netsparker’s way of giving back to you. Open source projects such as OpenCart have already used our free, automated web application security scans with great success. Why not you, too?
*** This is a Security Bloggers Network syndicated blog from Netsparker, Web Application Security Scanner authored by Robert Abela. Read the original post at: http://feedproxy.google.com/~r/netsparker/~3/x6wwSsFwlcw/