-
Notifications
You must be signed in to change notification settings - Fork 176
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
security: bump snakeyaml dep to 2.0 #82
Conversation
This PR is a minimal change to eliminate the CVE-2022-1471, but in my opinion it would be better to remove the runtime dependency as I did with #83 |
@bpossolo can we please have this merged and released? This is causing critical vulnerability alerts on this lib |
@mattrobenolt could you please review those changes so we can eliminate a CVE? |
What. I don't know Java. Not sure why I got pinged for this. |
Can anyone please approve this? |
done in a fork and released here https://github.com/olamy/uap-java |
Seems that with the version bump, there is no deprecation of the methods used, and the tests are passing. The only concern might be a performance benchmark between the old and the new version. Anyway, even this should be an quick and easy check. I will be blunt. I don't understand why such a simple fix of a critical/high cve in a widely used library (we can discuss if the score is accurate, but marking this as fp is not worth the time to discuss with security teams) is taking so long. This project needs more maintainers! @mattrobenolt you were pinged probably because you appear as the sole person in the ua-parser organization. Yes, it is possible to do something like the following, but some vulnerability checkers will also read the uap-java pom and still consider it vulnerable.
|
About performance: |
It would be great to have a bump fix or a radical fix like yours in an official release. @bpossolo could you check this issue? |
snakeyml has been updated to 2.2 and is included in uap-java release 1.6.0 |
Fixes: #81