-
Notifications
You must be signed in to change notification settings - Fork 118
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
Vulnerability warnings in maven repository #201
Comments
Hi @DeniseSl22 - Good catch. I'll add it to my long list of things to do in my life. If you're in a hurry you could test with the Xerces 2.12.2 and see how well things work and submit a PR. |
@hunterhacker thank you for getting back to me so quickly! I know the feeling of long to-do lists. If I have time I will give it a PR a try (but can't make any promises). |
What could be more important than this @hunterhacker ! ... plenty of things I'm sure, but would really appreciate if this could be addressed... any idea when you will be able to look into it? |
Both vulnerabilities seem to be build time vulnerabilities against Xerces 2.11 not required at runtime. Nothing to worry about IMO, but of course, I can foresee QSAs jumping out of joy with these nice new two entries in their reports. I tried latest version 2.12.2 that dragged me to upgrade xml-apis to 1.3.04 and just 26 out of 1093 failed. I'm attaching attaching the JUnit reports for the existing an upgraded runs, so that you can gauge the caliber of the changes that might be involved in upgrading these libraries. Existing versionNew Xerces and XML-APISI can send a PR if you want those handy @hunterhacker . |
Dear @hunterhacker , I just noticed these two warnings here:
The text was updated successfully, but these errors were encountered: