Bug 1997161 (CVE-2021-39365) - CVE-2021-39365 grilo: missing TLS certificate verification
Summary: CVE-2021-39365 grilo: missing TLS certificate verification
Alias: CVE-2021-39365
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1997162 Red Hat1997232 Red Hat1997233 Red Hat1997234
Blocks: Embargoed1997163
TreeView+ depends on / blocked
Reported: 2021-08-24 14:17 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-11-10 01:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-11-10 01:24:31 UTC

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4339 0 None None None 2021-11-09 18:19:39 UTC

Description Guilherme de Almeida Suckevicz 2021-08-24 14:17:57 UTC
In GNOME grilo though 0.3.13, grl-net-wc.c does not enable TLS certificate verification on the SoupSessionAsync objects it creates, leaving users vulnerable to network MITM attacks. NOTE: this is similar to CVE-2016-20011.


Comment 1 Guilherme de Almeida Suckevicz 2021-08-24 14:18:12 UTC
Created grilo tracking bugs for this issue:

Affects: fedora-all [bug 1997162]

Comment 2 Bastien Nocera 2021-08-24 15:35:41 UTC
Fedora 33 update:

That was the last supported version of Fedora to be potentially vulnerable.

Comment 3 Garrett Tucker 2021-08-24 16:53:59 UTC
RHEL 9 is not affected as the patch listed above has been applied. However, RHEL 8.5.0 and below is affected by this and should have the patch applied but is delegated to the engineering teams.

Comment 5 errata-xmlrpc 2021-11-09 18:19:38 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2021:4339 https://access.redhat.com/errata/RHSA-2021:4339

Comment 6 Product Security DevOps Team 2021-11-10 01:24:29 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


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