[
https://issues.apache.org/jira/browse/JEXL-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980923#comment-15980923
]
Henri Biestro commented on JEXL-223:
------------------------------------
I dont understand either; any public method is callable though scripting.
As a side-note, controlling what is allowed through JEXL can be tailored
through 3 features that hide/control which classes JEXL is allowed to
introspect:
- using a specific ClassLoader
- operating through a Sandbox
- annotating classes/methods/fields with @NoJexl
Old but mostly relevant:
http://stackoverflow.com/questions/6551073/how-do-you-create-a-secure-jexl-scripting-sandbox/6551087#6551087
> Apache Commons JEXL Expression Execute Command Vulnerabilitity
> --------------------------------------------------------------
>
> Key: JEXL-223
> URL: https://issues.apache.org/jira/browse/JEXL-223
> Project: Commons JEXL
> Issue Type: Bug
> Reporter: cnbird
> Priority: Critical
>
> 0x01 Summary
> Apache Commons JEXL Expression Execute Command Vulnerabilitity throught
> groovy.
> 0x02 POC
> POC Report to Apache Security Email Address [email protected].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
