-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
net.minidev.json.parser.ParseException: Malicious payload, having non natural depths. #154
Comments
@brad302 I think it has been discussed this in #131 (comment) |
I think this error only occurs when json size very large. Could you please provide a minimal reproduced case? |
Yep, have attached one. When I say "innocuous" I mean, I would expect it to be able to be processed. I consider the payload to be large enough but I have seen much larger. Let me know how you go. Thanks |
What are the chances of having the default value substantially increased? My issue is, when this new version is released, there's nothing to say that Talend will follow suit and provide the ability to enter a value and override the default. It may be a big ask but something like 2000 (rather than 400) would help a lot. I'd say that would still alleviate any issues relating to a DDOS attack but not sure if it would then re-expose the CVE. Happy to get your thoughts. |
If a real non-malicious application needs more, adding a flag to drop this security may be a better choice, and increasing the current 400 to more like 1000, is fine, 400 never blew up any stack, and 1000 is still kind of okay. |
discussions are in progress in the draft #155 |
I think we can close this issue now, see #156 to drop the limit. |
As I'm sure you're aware, this package is used by Talend by two key components, tExtractJSONFields and tFileInputJSON.
We're currently upgrading to Talend V8 which brings with it v2.4.9 of this package after having been on v2.4.7 for quite some time.
Can I ask why that exception was introduced because at present, it's halting our upgrade. We have a seemingly innocuous sized JSON structure that is now failing because of the package upgrade.
My question is, how can we possibly overcome it? It's quite the issue.
Thanks
Brad
The text was updated successfully, but these errors were encountered: