Azure Load Testing
An Azure service that enables developers and testers to generate insights on how to improve the performance, scalability, and capacity usage of their application
40 questions
ERROR o.a.j.e.j.j.JSONPostProcessor: net.minidev.json.parser.ParseException: Malicious payload, having non natural depths
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 72%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
Volodymyr Martynenko
25
Reputation points
Hi,
since yesterday evening I've started seeing the following exception
ERROR o.a.j.e.j.j.JSONPostProcessor: net.minidev.json.parser.ParseException: Malicious payload, having non natural depths
when running my Azure Load Tests. It only occurs for big responses, especially the ones including JSONs with multiple nesting levels.
Previously everything was working fine and when I run my test locally this exception doesn’t occur.
I've found an article - https://github.com/karatelabs/karate/issues/2277 saying that there were some limitations introduced to the library net.minidev.json which is used by this extractor. Also it is described in https://libraries.io/maven/net.minidev:json-smart
Please, kindly assist in resolving the issue.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 28.999999999999996%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELC%3C/text%3E%3C/svg%3E)
Lloyd Cheung 0 Reputation points2023-06-29T00:32:46.85+00:00 I have the same issue too. Will json-smart be updated to version 2.4.10 soon?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 90%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
Vithyatharan Surya Sekar 0 Reputation points2023-07-06T06:00:46.0966667+00:00 I'm currently facing an issue while writing a test script using the JMeter tool. Specifically, the problem arises in a PUT API call. First, I've attempted to retrieve the response data from a preceding GET call and store it in a variable. Then, I pass this variable to a subsequent PUT API call using the JSR223 Preprocessor in JMeter, leveraging Groovy code.
In my Groovy code, I've made multiple attempts to convert a potentially malicious payload into a valid one. I've experimented with various techniques such as data manipulation, payload transformation, and encoding methods. However, despite my diligent efforts, none of the attempted malicious payloads or data conversions have proven successful in resolving the issue.
I'm currently seeking assistance or advice on how to overcome this problem and successfully execute the PUT API call within my JMeter test script.
The same setup seems to still work fine in my local setup and is only failing via Azure.
-
Vithyatharan Surya Sekar 0 Reputation points
2023-07-06T06:03:02.87+00:00 The same setup seems to still work fine in my local setup and is only failing via Azure.
Sign in to comment