Over a million developers have joined DZone.

Struts2 Vulnerabilities: Who Is Responsible? (Video and Podcast)

DZone's Guide to

Struts2 Vulnerabilities: Who Is Responsible? (Video and Podcast)

When there's a vulnerability in open source software, is it the reponsibility of the developers who created it, or the companies that adopt it?

· Security Zone
Free Resource

Discover how to provide active runtime protection for your web applications from known and unknown vulnerabilities including Remote Code Execution Attacks.

Update: This article was originally published on September 14, 2017. The same day, Kevin McGrail published an article on LinkedIn, Act II: Equifax tries and fails to throw Apache Struts under the Bus, where he, too, talks about how commercial companies might consider contributing financially to open source projects.

With the acknowledgment by Equifax that the massive breach of over 143 million customer records was caused by an unpatched vulnerability in Struts2, we try and slow down a bit to talk about who is responsible for this, the creators of the open source solutions or the people who use them? In this broadcast, we speak with David Blevins, CEO of TomiTribe and Brian Fox, CTO of Sonatype.

If you can't view YouTube videos, you can listen to the entire podcast, Struts2 Vulnerabilities: Who Is Responsible on the OWASP 24/7 Podcast Channel.

Find out how Waratek’s award-winning application security platform can improve the security of your new and legacy applications and platforms with no false positives, code changes or slowing your application.

security ,devsecops ,equifax ,apache struts 2

Published at DZone with permission of Mark Miller, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}