struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raintung Li (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WW-4647) Security: OGNL can change the MemberAccess in OGNLContext
Date Fri, 17 Jun 2016 03:54:05 GMT

     [ https://issues.apache.org/jira/browse/WW-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raintung Li updated WW-4647:
----------------------------
    Attachment: SecurityOGNLContext.java

This is simple to make securityOGNLContext

> Security: OGNL can change the MemberAccess in OGNLContext
> ---------------------------------------------------------
>
>                 Key: WW-4647
>                 URL: https://issues.apache.org/jira/browse/WW-4647
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Core Actions
>    Affects Versions: 2.3.20
>            Reporter: Raintung Li
>            Priority: Critical
>         Attachments: SecurityOGNLContext.java
>
>
> OGNL example: S2-029 leak: 
> #_memberAccess.excludedClasses=#{}.keySet() it has been fixed.
> But now we can direct change the _memberAccess in the OGNLContext
> #_memberAccess=@ognl.OgnlContext@DEFAULT_MEMBER_ACCESS
> woo.. it can round the SecurityMemberAccess.isAccessible checking, because modify the
OGNLContext member _memberaccess that NOT check the accessible.
> Struts should be self extend the OGNLContent to make securityOGNLContect to keep safe.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message