You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Yauheni Sidarenka (JIRA)" <ji...@apache.org> on 2017/03/28 16:48:41 UTC

[jira] [Commented] (SHIRO-619) CVE-2014-0114 needs to be addressed properly if it is possible

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

Yauheni Sidarenka commented on SHIRO-619:
-----------------------------------------

As I can see, _BeanUtilsBean_ is used indirectly at least in _org.apache.shiro.config.ReflectionBuilder_ in _shiro-core_.

> CVE-2014-0114 needs to be addressed properly if it is possible
> --------------------------------------------------------------
>
>                 Key: SHIRO-619
>                 URL: https://issues.apache.org/jira/browse/SHIRO-619
>             Project: Shiro
>          Issue Type: Bug
>    Affects Versions: 1.3.2, 1.4.0-RC2
>            Reporter: Yauheni Sidarenka
>
> This issue stems from https://issues.apache.org/jira/browse/SHIRO-576.
> In my humble opinion, it is not enough just to set the version of commons-beanutils to 1.9.2 or to 1.9.3 in order to fix CVE-2014-0114 vulnerability because mentioned versions *DO NOT* fix it by default. In contrast, the fix should be applied explicitly by beanutils-consuming applications (see INTRODUCTION section in http://commons.apache.org/proper/commons-beanutils/javadocs/v1.9.2/RELEASE-NOTES.txt).
> So, if Shiro uses _BeanUtilsBean_ somehow and is vulnerable to mentioned CVE, it would be worth to configure _BeanUtilsBean_ as it is recommended in beanutils' release notes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)