Bug 1375303 – gnutls trusts a certificate whose CA is both explicitly trusted and blacklisted

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	gnutls (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	Nikos Mavrogiannopoulos
QA Contact:	Stanislav Zidek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1377248
	Show dependency tree / graph

Reported:	2016-09-12 12:36 EDT by Stanislav Zidek
Modified:	2017-08-01 04:48 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	gnutls-3.3.26-1.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-01 04:48:22 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:2292	normal	SHIPPED_LIVE	Moderate: gnutls security, bug fix, and enhancement update	2017-08-01 08:39:15 EDT

Groups: None (edit)

Description Stanislav Zidek 2016-09-12 12:36:02 EDT

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):
gnutls-3.3.24-1.el7

How reproducible:
always

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 04:48:22 EDT

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/RHSA-2017:2292

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