Bug 1870056 (CVE-2020-24331) - CVE-2020-24331 trousers: tss user still has read and write access to the /etc/tcsd.conf file if tcsd is started as root
Summary: CVE-2020-24331 trousers: tss user still has read and write access to the /etc...
Alias: CVE-2020-24331
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1870057 1882401 1882402 1972196 1972197
Blocks: 1849039
TreeView+ depends on / blocked
Reported: 2020-08-19 09:40 UTC by Marian Rehak
Modified: 2023-09-26 17:50 UTC (History)
4 users (show)

Fixed In Version: trousers 0.3.14
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-05-18 20:34:44 UTC

Attachments (Terms of Use)

Description Marian Rehak 2020-08-19 09:40:30 UTC
If the tcsd daemon is started with root privileges, the tss user still has read and write access to the /etc/tcsd.conf file (which contains various settings related to this daemon).

External Reference:


Comment 1 Marian Rehak 2020-08-19 09:40:54 UTC
Created trousers tracking bugs for this issue:

Affects: fedora-all [bug 1870057]

Comment 2 Marco Benatto 2020-09-24 13:27:04 UTC
Upstream commit for this issue:


Comment 4 Marco Benatto 2020-09-24 13:44:38 UTC
There's an issue on trousers. If trousers daemon is started using root user the default, tss unprivileged user still can write to the configuration file due to missing checks at conf_file_init() function. As tcsd.conf holds a set of sensitive configuration entries for the daemon, an attacker can use that to cause DoS, compromise confidentiality or integrity of several system data.

Comment 5 errata-xmlrpc 2021-05-18 13:48:32 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

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

Comment 6 Product Security DevOps Team 2021-05-18 20:34:44 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.