Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When a token is received and either unwrapped or verified (as appropriate to the token), Kerberos will mark all packets after the first one as duplicates. For GSS, this does not cause an exception, but if an app relies on the property flags for message details (such as duplicate, old, out of order, etc), then the app will always find these incoming packets to be duplicates.
The underlying cause is that sun/security/jgss/krb5/MessageToken_v2.java always obtains the sequence number from the start of the message, which is fixed, rather than from its specified location.
Version-Release number of selected component (if applicable):
1.8.0.212.b04-0.el6_10. Probably also earlier versions.
How reproducible:
Always
Steps to Reproduce:
1. Create a GSS context
2. Generate multiple tokens of the same kind (MIC or wrap)
3. Verify or unwrap said tokens and pay attention to the duplicate flag on the message prop after unwrapping.
Actual results:
The first token is not flagged, but all subsequent tokens are.
Expected results:
"Duplicate" should only be set if the same token is verified or unwrapped more than once.
Additional info:
This bug exists in the baseline code until it is fixed in release 11.
This also affects Oracle Java, probably for the same range.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1071