You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sridhar Sarnobat (Jira)" <ji...@apache.org> on 2022/10/08 00:41:00 UTC

[jira] [Commented] (BEANUTILS-520) Mitigate CVE-2014-0114

    [ https://issues.apache.org/jira/browse/BEANUTILS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17614309#comment-17614309 ] 

Sridhar Sarnobat commented on BEANUTILS-520:
--------------------------------------------

Is there a workaround for commons-beanutils 1.8.0? Upgrading will happen eventually but I'd like to know if there is a direct way to stop the vulnerability in the meantime.

(we aren't using Struts)

> 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
(v8.20.10#820010)