Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
framework-1.8.1
-
None
Description
In SecureAction we capture the calling context for optimization purposes, but the context captures the current stack no matter who is on the stack. Since the whole point of SecureAction is to allow the framework to perform sensitive operations without worrying about who is on the call stack, this seems to be a bug since there could be someone with lower privileges on the stack. I think we need to capture the calling context inside a privileged block.