Updated recommendations for avoiding JEXL injections

This commit is contained in:
Artem Smotrakov
2021-03-03 11:40:59 +01:00
committed by GitHub
parent c243f2f042
commit 7cc7ec962e

View File

@@ -14,8 +14,8 @@ and then evaluated, then it may allow the attacker to run arbitrary code.
<recommendation>
<p>
Including untrusted input in a JEXL expression should be avoided. If it is not possible,
JEXL expressions should be run in a sandbox that allows accessing only
It is generally recommended to avoid using untrusted input in a JEXL expression.
If it is not possible, JEXL expressions should be run in a sandbox that allows accessing only
explicitly allowed classes.
</p>
</recommendation>
@@ -60,4 +60,4 @@ that checks if callees are instances of allowed classes.
<a href="https://owasp.org/www-community/vulnerabilities/Expression_Language_Injection">Expression Language Injection</a>.
</li>
</references>
</qhelp>
</qhelp>