You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-u URL, --url URL The URL of the page to access and attempt to pull viewstate and generator from
226
+
-p PROXY, --proxy PROXY
227
+
Optionally specify an HTTP proxy
228
+
-a USER_AGENT, --user-agent USER_AGENT
229
+
Optionally set a custom user-agent
230
+
-m, --machine-keys Optionally include ASP.NET MachineKeys when loading keys
231
+
-f, --force Force enumeration of vulnerable AsyncUpload endpoint without user confirmation
232
+
-v VERSION, --version VERSION
233
+
Specify a custom Telerik version to test
234
+
-c CUSTOM_KEYS, --custom-keys CUSTOM_KEYS
235
+
Specify custom keys in format 'encryptionkey,hashkey'. When provided, only these keys will be tested.
236
+
-d, --debug Enable debug mode to show detailed request information
237
+
--modern-dialog-params
238
+
Use modern dialog parameters format (may work better for newer Telerik versions 2018+)
239
+
240
+
```
241
+
218
242
Fully functional CLI example for identifying known Telerik Hash keys (`Telerik.Upload.ConfigurationHashKey`) and Encryption keys (`Telerik.Web.UI.DialogParametersEncryptionKey`) used with Telerik DialogHandler instances for Post-2017 versions (those patched for CVE-2017-9248), and brute-forcing version / generating exploitation DialogParameters values.
219
243
220
244
Currently, this appears to be the only tool capable of building a working exploit URL for"patched" versions of Telerik.
0 commit comments