Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vunerability for commons-fileupload version 1.3 (CVE-2014-0050) #939

Open
raux opened this issue Nov 25, 2015 · 0 comments
Open

Vunerability for commons-fileupload version 1.3 (CVE-2014-0050) #939

raux opened this issue Nov 25, 2015 · 0 comments

Comments

@raux
Copy link

raux commented Nov 25, 2015

I apologize for the spam. I am now opening my email as an issue. Please find my email below. We want to use this experience to help us understand the factors involved in bumping a library version.

My name is Raula Kula, a research assistant prof at Osaka University, Japan. Currently I am studying the maintenance of Maven Libraries. I am currently focused on OSS vulnerabilities and the varying reasons for library migration.

As a part of my study I particularity focused on the commons-fileupload library. http://commons.apache.org/proper/commons-fileupload/ and the CVE-2014-0050 https://www.cvedetails.com/cve/CVE-2014-0050/, announced on 2014-04-01, which affects versions up to 1.3.

We noticed that your project on Github is still configured to depend on a vulnerable version of fileupload (1.2.2) at https://github.com/ippontech/tatami/blob/master/pom.xml.

We understand that there are many reasons for not migrating, thus we be appreciate if you could simply detail the following:

  1. Were you aware of the vulnerability? If so, then how long ago.
  2. What are some factors that influence you not to update.

Also feel free to detail any other information to help us understand your decision. Again, thank you for taking your time off your busy schedule and hope to hear from you soon.

Sincerely,
Raula

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant