Bug 1375303 - gnutls trusts a certificate whose CA is both explicitly trusted and blacklisted
Summary: gnutls trusts a certificate whose CA is both explicitly trusted and blacklisted
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnutls
Version: 7.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Nikos Mavrogiannopoulos
QA Contact: Stanislav Zidek
Depends On:
Blocks: 1377248
TreeView+ depends on / blocked
Reported: 2016-09-12 16:36 UTC by Stanislav Zidek
Modified: 2017-08-01 08:48 UTC (History)
1 user (show)

Fixed In Version: gnutls-3.3.26-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-08-01 08:48:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2292 0 normal SHIPPED_LIVE Moderate: gnutls security, bug fix, and enhancement update 2017-08-01 12:39:15 UTC

Description Stanislav Zidek 2016-09-12 16:36:02 UTC
Description of problem:
If I add my custom CA to both /etc/pki/ca-trust/source/anchors and /etc/pki/ca-trust/source/blacklist (and run update-ca-trust), certificates signed by this CA are trusted.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. generate a CA and a server cert signed by it
2. add the CA to both /etc/pki/ca-trust/source/anchors and /etc/pki/ca-trust/source/blacklist
3. update-ca-trust
4. verify server cert (certtool --verify <server.pem)

Actual results:
Chain verification output: Verified. The certificate is trusted.

Expected results:
Blacklist has priority, server cert is not trusted.

Additional info:
I did further investigation and it really seems that the issue is only in this corner case. Blacklisting CA that is included in system by default works as expected.

Comment 7 errata-xmlrpc 2017-08-01 08:48:22 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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