Bug 1903590 (CVE-2020-29362) - CVE-2020-29362 p11-kit: out-of-bounds read in p11_rpc_buffer_get_byte_array function in rpc-message.c
Summary: CVE-2020-29362 p11-kit: out-of-bounds read in p11_rpc_buffer_get_byte_array f...
Alias: CVE-2020-29362
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1909019 1906815 1907910 1907913 1909022
Blocks: 1902080
TreeView+ depends on / blocked
Reported: 2020-12-02 12:58 UTC by Guilherme de Almeida Suckevicz
Modified: 2021-05-18 20:37 UTC (History)
8 users (show)

Fixed In Version: p11-kit 0.23.22
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-18 20:37:50 UTC

Attachments (Terms of Use)

Description Guilherme de Almeida Suckevicz 2020-12-02 12:58:32 UTC
The p11_rpc_buffer_get_byte_array function can read up to four bytes past the end of a heap allocation due to an incorrect bounds check, caused by a confusion between two similarly-named variables.

Comment 2 Guilherme de Almeida Suckevicz 2020-12-15 13:55:41 UTC
Created mingw-p11-kit tracking bugs for this issue:

Affects: fedora-all [bug 1907910]

Created p11-kit tracking bugs for this issue:

Affects: fedora-all [bug 1907913]

Comment 3 Cedric Buissart 2020-12-18 08:16:11 UTC
External References:


Comment 8 Cedric Buissart 2021-01-11 15:21:58 UTC

The p11-kit library is primarily intended to be used locally, in which case the attacker needs to have sufficient permission to access the p11-kit communication. Although there may be use cases of p11-kit being used with a remote entity, all parties must be considered trusted.
As a result, Red Hat considers this vulnerability with a Medium severity.

Comment 9 errata-xmlrpc 2021-05-18 13:40:12 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

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

Comment 10 Product Security DevOps Team 2021-05-18 20:37:50 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.