-
Notifications
You must be signed in to change notification settings - Fork 333
Potential SnakeYaml version upgrade issue #5818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Minor clarification: ORT is not using SnakeYaml directly, but ORT is using Jackson which in turn uses SnakeYaml.
That limit was introduced as part of SnakeYaml 1.32. However, I just verified that ORT's
This sentence confuses me now, because the 3MB limit has been introduced with version 1.32. So using version 1.31 (as we do) should be fine. Can you please clarify? |
We will eventually want to upgrade anyway and I could not find a way to override the limit. Not being able to parse YAML files larger than 3MB would make the file format useless for us so I have asked the devs if they can confirm that my assumption is correct: FasterXML/jackson-dataformats-text#335 (comment) |
As explained here we could always use Gradle to force the transitive SnakeYaml version to 1.31 (or even 1.30), as most users probably aren't affected by the evoked CVEs anyway. PS: Slightly off-topic, but with all the removals of the custom deserializers recently, I'm really looking forward to #3904 which would solve also this issue for good. |
Efforts to make the size limit configurable are now tracked in FasterXML/jackson-dataformats-text#337. |
Apart from potential technical issues we would first have to migrate all config files to use camel case, I think that's still a long way to go. |
For background information see [1]. [1]: #5818 Signed-off-by: Sebastian Schuberth <[email protected]>
For background information see [1]. [1]: #5818 Signed-off-by: Sebastian Schuberth <[email protected]>
Stick to version 1.31, which is the latest version that does not limit the file size to 3 MiB, also see the discussion at [1]. [1]: oss-review-toolkit/ort#5818 Signed-off-by: Sebastian Schuberth <[email protected]>
Stick to version 1.31, which is the latest version that does not limit the file size to 3 MiB, also see the discussion at [1]. [1]: oss-review-toolkit/ort#5818 Signed-off-by: Sebastian Schuberth <[email protected]>
Stick to version 1.31, which is the latest version that does not limit the file size to 3 MiB, also see the discussion at [1]. [1]: #5818 Signed-off-by: Sebastian Schuberth <[email protected]>
Stick to version 1.31, which is the latest version that does not limit the file size to 3 MiB, also see the discussion at [1]. [1]: #5818 Signed-off-by: Sebastian Schuberth <[email protected]>
This new feature is being made use of in #6124. |
The latest release versions of SnakeYaml, the YML parser used by ORT, it is no longer possible to parse ORT files larger than 3 MB in size
The symptom is an exception similar to this:
The problem seems to be introduced as part of the fix for CVE-2022-25857
There is currently no other workaround except fixing the snakeyaml version to 1.30
The text was updated successfully, but these errors were encountered: