epugh opened a new pull request, #193: URL: https://github.com/apache/solr-site/pull/193
Many of the vex entries have open ended verisons like "x.x-today", that made sense when first written, but time has passed. Leveraging some AI support, and some manual poking I went and update the "today" to which specific of version of Solr is actually impacted by the vulnerablity. I eliminated the tika core entry, it was VERY vague, and I couldn't map it any real CVE. The other velocity tools entry I tied it to the underlying struts cves that are what was triggering the vulnerablity. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
