struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Husted (JIRA)" <>
Subject [jira] Updated: (WW-2316) Ability to prevent method:METHOD_NAME access
Date Mon, 14 Jan 2008 17:28:04 GMT


Ted Husted updated WW-2316:

    Issue Type: Sub-task  (was: Improvement)
        Parent: WW-2363

> Ability to prevent method:METHOD_NAME access
> --------------------------------------------
>                 Key: WW-2316
>                 URL:
>             Project: Struts 2
>          Issue Type: Sub-task
>          Components: Dispatch Filter
>    Affects Versions: 2.0.11, 2.1.0
>            Reporter: Dale Newfield
>             Fix For: 2.1.1
> In order to allow multiple form submission buttons result in different behavior based
on the button pressed, a specially named parameter is included in the form submission that
instructs the ActionMapper to call a method indicated in the URL.  This special parameter
can be used to implement a credential escalation attack, though:  If a user has suffiicient
credentials to call a single method on an action, this provides a mechanism whereby they could
call any method on that action.  The "action!" capability introduces a similar vulnerability,
and the "allowDynamicMethodCalls" option closes that hole.  Besides needing to provide a different
mechanism to allow different form submission buttons to do different things, is there a large
downside to using this same option ("allowDynamicMethodCalls") to close this hole as well?
> (Just to be explicit, that solution would wrap "if (allowDynamicMethodCalls) {" and "}"
around lines 186-188 in .)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message