[
https://issues.apache.org/jira/browse/WW-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335376#comment-15335376
]
Lukasz Lenart commented on WW-4647:
-----------------------------------
This was already fixed by changing how Struts is using OGNL and disabling
access to arithmetic operations. And next time please report any security
vulnerabilities to [email protected] - making them public (as here) is
irresponsible and makes hacker's life easier. I'm going to delete this issue.
> 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
> Fix For: 2.3.30, 2.5.2
>
> 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
> #[email protected]@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)
