You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Melloware (JIRA)" <ji...@apache.org> on 2019/08/18 15:30:00 UTC
[jira] [Commented] (BEANUTILS-520) BeanUtils2 mitigate
CVE-2014-0114
[ https://issues.apache.org/jira/browse/BEANUTILS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16909995#comment-16909995 ]
Melloware commented on BEANUTILS-520:
-------------------------------------
[~ggregory] or [~chtompki] what needs to be done to get a Beanutils 2.0 released? What open work is left? The reason I am interested is it uses Commons Collections 4 and allows me to stop using Collections 3. It will also allow for upgrade of Commons Configuration2 to use Beanutils2 and also stop relying on Commons Collection 3.
> BeanUtils2 mitigate CVE-2014-0114
> ---------------------------------
>
> Key: BEANUTILS-520
> URL: https://issues.apache.org/jira/browse/BEANUTILS-520
> Project: Commons BeanUtils
> Issue Type: Improvement
> Components: Bean / Property Utils
> Affects Versions: 1.9.3
> Reporter: Melloware
> Assignee: Rob Tompkins
> Priority: Major
> Labels: security
> Fix For: 1.9.4, 2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> https://nvd.nist.gov/vuln/detail/CVE-2014-0114
> Due to the above CVE in 1.9.2 they added a Suppression but it is still being marked as a security risk through most major checks from OWASP and Sonatype IQ.
> "commons-beanutils added a SuppressPropertiesBeanIntrospector which includes a specialized instance of itself as the SUPPRESS_CLASS constant beginning in version 1.9.2 that specifically suppresses the class property. +However, this fix is not enabled by default.+"
> For BeanUtils2 why not make this the default and have people "enable" it if it they want to get the feature.
> Thanks for your consideration.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)