[jira] [Created] (SOLR-17303) CVE-2023-39410: Upgrade to apache-avro version 1.11.3
Sujeet-A created SOLR-17303: --- Summary: CVE-2023-39410: Upgrade to apache-avro version 1.11.3 Key: SOLR-17303 URL: https://issues.apache.org/jira/browse/SOLR-17303 Project: Solr Issue Type: Bug Security Level: Public (Default Security Level. Issues are Public) Components: security Affects Versions: 9.6 Reporter: Sujeet-A CVE-2023-39410: Upgrade Apache-Avro version to 1.11.3 When deserializing untrusted or corrupted data, it is possible for a reader to consume memory beyond the allowed constraints and thus lead to out of memory on the system. This issue affects Java applications using Apache Avro Java SDK up to and including 1.11.2. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Commented] (SOLR-16568) Update woodstox-core to 6.4.0 to mitigate CVE-2022-40152
[ https://issues.apache.org/jira/browse/SOLR-16568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702095#comment-17702095 ] Sujeet-A commented on SOLR-16568: - Still getting these solr dockerhub.io images. !image-2023-03-18-15-37-50-431.png|width=946,height=261! > Update woodstox-core to 6.4.0 to mitigate CVE-2022-40152 > > > Key: SOLR-16568 > URL: https://issues.apache.org/jira/browse/SOLR-16568 > Project: Solr > Issue Type: Task >Affects Versions: 9.1 >Reporter: Bill Kidwell >Assignee: Kevin Risden >Priority: Minor > Labels: security > Fix For: main (10.0), 9.1.1 > > Attachments: image-2023-03-18-15-37-50-431.png > > Time Spent: 40m > Remaining Estimate: 0h > > This was brought up on the mailing list here: > https://lists.apache.org/thread/psc4r75o933y22jos4xk5rcwhof48sdw > The automatically created CVEs against xstream are misleading and read the > thread above to try to find out more. Its not clear which CVEs if any are > actually valid. > The only one that looks still valid against woodstox-core is CVE-2022-40152 > (https://github.com/advisories/GHSA-3f7h-mf4q-vrm4) and fixed in > https://github.com/FasterXML/woodstox/issues/160. It is LOW severity only. > > Our container scan detects woodstox 6.2.8 > /opt/bitnami/solr/server/solr-webapp/webapp/WEB-INF/lib/woodstox-core-6.2.8.jar -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
[jira] [Updated] (SOLR-16568) Update woodstox-core to 6.4.0 to mitigate CVE-2022-40152
[ https://issues.apache.org/jira/browse/SOLR-16568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sujeet-A updated SOLR-16568: Attachment: image-2023-03-18-15-37-50-431.png > Update woodstox-core to 6.4.0 to mitigate CVE-2022-40152 > > > Key: SOLR-16568 > URL: https://issues.apache.org/jira/browse/SOLR-16568 > Project: Solr > Issue Type: Task >Affects Versions: 9.1 >Reporter: Bill Kidwell >Assignee: Kevin Risden >Priority: Minor > Labels: security > Fix For: main (10.0), 9.1.1 > > Attachments: image-2023-03-18-15-37-50-431.png > > Time Spent: 40m > Remaining Estimate: 0h > > This was brought up on the mailing list here: > https://lists.apache.org/thread/psc4r75o933y22jos4xk5rcwhof48sdw > The automatically created CVEs against xstream are misleading and read the > thread above to try to find out more. Its not clear which CVEs if any are > actually valid. > The only one that looks still valid against woodstox-core is CVE-2022-40152 > (https://github.com/advisories/GHSA-3f7h-mf4q-vrm4) and fixed in > https://github.com/FasterXML/woodstox/issues/160. It is LOW severity only. > > Our container scan detects woodstox 6.2.8 > /opt/bitnami/solr/server/solr-webapp/webapp/WEB-INF/lib/woodstox-core-6.2.8.jar -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
