Gentoo: GLSA-202107-39: Apache Commons FileUpload: Multiple vulnerabilities
Summary
Multiple vulnerabilities have been discovered in Apache Commons FileUpload. Please review the CVE identifiers referenced below for details.
Resolution
Gentoo has discontinued support for Apache Commons FileUpload. We
recommend that users unmerge it:
# emerge --ask --depclean "dev-java/commons-fileupload"
NOTE: The Gentoo developer(s) maintaining Apache Commons FileUpload
have discontinued support at this time. It may be possible that a new
Gentoo developer will update Apache Commons FileUpload at a later date.
We do not have a suggestion for a replacement at this time.
References
[ 1 ] CVE-2013-0248 https://nvd.nist.gov/vuln/detail/CVE-2013-0248 [ 2 ] CVE-2014-0050 https://nvd.nist.gov/vuln/detail/CVE-2014-0050 [ 3 ] CVE-2016-3092 https://nvd.nist.gov/vuln/detail/CVE-2016-3092
Availability
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202107-39
Concerns
Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.
Background
The Apache Commons FileUpload package makes it easy to add robust, high-performance, file upload capability to your servlets and web applications.
Affected Packages
------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-java/commons-fileupload <= 1.3 Vulnerable! ------------------------------------------------------------------- NOTE: Certain packages are still vulnerable. Users should migrate to another package if one is available or wait for the existing packages to be marked stable by their architecture maintainers.
Impact
===== Please review the referenced CVE identifiers for details.
Workaround
There is no known workaround at this time.