Bug 2236592

Summary:	Update to 17.0.8.1 Interim Release to Fix Regression in Zip64 Handling [rhel-9]
Product:	Red Hat Enterprise Linux 9	Reporter:	Andrew John Hughes <ahughes>
Component:	java-17-openjdk	Assignee:	Andrew John Hughes <ahughes>
Status:	CLOSED MIGRATED	QA Contact:	OpenJDK QA <java-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.2	CC:	sfroberg
Target Milestone:	rc	Keywords:	MigratedToJIRA, Triaged, ZStream
Target Release:	9.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	java-17-openjdk-17.0.8.1.1-2.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2237185 2237186 (view as bug list)		Environment:
Last Closed:	2024-05-11 00:23:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2237185, 2237186

Description Andrew John Hughes 2023-08-31 20:58:22 UTC

A security fix (JDK-8302483: Enhance ZIP performance) introduced extra checks on Zip64 zip files, which regressed the JDK's ability to read certain zip files:

https://bugs.openjdk.org/browse/JDK-8313765

This has been fixed upstream in an interim 17.0.8.1 release.

We should update to this interim release as soon as possible and before the October security update where possible.

Comment 5 RHEL Program Management 2024-05-11 00:18:26 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2024-05-11 00:23:26 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.