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.
+++ This bug was initially created as a clone of Bug #1758587 +++
Description of problem:
When the ciphertext is too small to contain IV, MAC and padding, openssl will send decryption_failed alert instead of the bad_record_mac.
This happens only for ciphers that do not use the "stiched" implementation of a cipher that combines the symmetric cipher with the HMAC.
Version-Release number of selected component (if applicable):
openssl-1.1.1c-2.el8
How reproducible:
always
Steps to Reproduce:
1. send a 16 bytes long ciphertext in a TLS record after negotiating TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 or TLS_RSA_WITH_3DES_EDE_CBC_SHA
Actual results:
server replies with decryption_failed
Expected results:
bad_record_mac alert
Additional info:
since the check is based on publicly visible data (the length of ciphertext), the difference in alert returned can't be used as a padding oracle for decryption
--- Additional comment from Tomas Mraz on 2019-10-04 15:05:00 UTC ---
Trivial fix.