If an X.509 certificate has a malformed IPAddressFamily extension, OpenSSL could do a one-byte buffer overread. The most likely result would be an erroneous display of the certificate in text format. External References: https://www.openssl.org/news/secadv/20170828.txt References: https://github.com/openssl/openssl/pull/4276
Created mingw-openssl tracking bugs for this issue: Affects: epel-7 [bug 1486145] Affects: fedora-all [bug 1486147] Created openssl tracking bugs for this issue: Affects: fedora-all [bug 1486146]
CVSS3 Base Score is 5.3 (https://access.redhat.com/security/cve/cve-2017-3735), which means RedHat is failed on PCI compliance (pg. 31 in https://www.pcisecuritystandards.org/documents/ASV_Program_Guide_v3.0.pdf I believe RedHat don't want to leave the customers failed on PCI compliance. I'm using the Amazon Linux AMI so it's following RHEL/EPEL 6. Please address this ASAP.
Statement: This flaw only exhibits itself when: 1. OpenSSL is used to display details of a local or a remote certificate. 2. The certificate contains the uncommon RFC 3779 IPAddressFamily extension. The maximum impact of this flaw is garbled information being displayed, there is no impact on the availability of service using such a certificate. Also this flaw can NOT be used to create specially-crafted certificates. Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2018:3221 https://access.redhat.com/errata/RHSA-2018:3221