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.
Bug 2169314 - openssl FIPS mode self-test should zeroize `out` in `verify_integrity` in providers/fips/self_test.c
Summary: openssl FIPS mode self-test should zeroize `out` in `verify_integrity` in pro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: openssl
Version: 9.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Clemens Lang
QA Contact: Alicja Kario
URL:
Whiteboard:
Depends On:
Blocks: 2175873 2175874 2175875
TreeView+ depends on / blocked
 
Reported: 2023-02-13 09:52 UTC by Clemens Lang
Modified: 2023-11-07 11:25 UTC (History)
4 users (show)

Fixed In Version: openssl-3.0.7-17.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2175873 2175874 2175875 (view as bug list)
Environment:
Last Closed: 2023-11-07 08:53:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-9564 0 None None None 2023-02-13 09:54:08 UTC
Red Hat Issue Tracker FIPS-77 0 None None None 2023-02-13 09:52:58 UTC
Red Hat Issue Tracker RHELPLAN-148401 0 None None None 2023-02-13 09:54:13 UTC
Red Hat Product Errata RHBA-2023:6627 0 None None None 2023-11-07 08:53:54 UTC

Description Clemens Lang 2023-02-13 09:52:58 UTC
Description of problem:
The `out` variable in `verify_integrity` in providers/fips/self_test.c is not zeroized, and the lab is advising us that it should be.

Apply

diff --git a/providers/fips/self_test.c b/providers/fips/self_test.c
index 10804d9f59..cd6cd44fd1 100644
--- a/providers/fips/self_test.c
+++ b/providers/fips/self_test.c
@@ -283,6 +283,7 @@ static int verify_integrity(OSSL_CORE_BIO *bio, OSSL_FUNC_BIO_read_ex_fn read_ex
         goto err;
     ret = 1;
 err:
+    OPENSSL_cleanse(out, sizeof(out));
     OSSL_SELF_TEST_onend(ev, ret);
     EVP_MAC_CTX_free(ctx);
     EVP_MAC_free(mac);

to fix this.


Version-Release number of selected component (if applicable):
openssl-3.0.1-44.el9_0.1

How reproducible:
Inspect source code

Actual results:
Variable is not zeroized

Expected results:
Variable is zeroized

Comment 14 errata-xmlrpc 2023-11-07 08:53:05 UTC
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 (openssl bug fix and enhancement update), 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-2023:6627


Note You need to log in before you can comment on or make changes to this bug.