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.
I believe the following issues related to integer overflows are purely cosmetic, but they might trip future static analysis efforts (if we ever get tools to automate this).
common/path.c:p11_path_build() has an overflow in the length computation if some of the input strings alias and are very long.
common/compat.c:strconcat() has an overflow in the length computation if some of the input strings alias and are very long.
common/url.c:p11_url_decode(): Check "value + 2 > end" is technically incorrect, should be "end - value < 2".
common/url.c:p11_url_encode(): should check for overflow in size computation (but this is purely cosmetic).
p11-kit/conf.c:read_config_file() has an overflow in the computation of the malloc length (on 32-bit systems).
common/base64.c:p11_b64_pton() should define tarindex as size_t. Return type would need fixing, too. Or targsize needs to be checked against INT_MAX.
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/RHEA-2017:1981