Pebble Templates 3.1.5 allows attackers to bypass a protection mechanism and implement arbitrary code execution with springbok. NOTE: the vendor disputes this because input to the Pebble templating engine is intended to include arbitrary Java code, and thus either the input should not arrive from an untrusted source, or else the application using the engine should apply restrictions to the input. The engine is not responsible for validating the input.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Link | Tags |
---|---|
https://github.com/Y4tacker/Web-Security/issues/3 | issue tracking exploit third party advisory |
https://github.com/PebbleTemplates/pebble/issues/625#issuecomment-1282138635 | issue tracking exploit third party advisory |