Skip to content
Fencer Intel
medium 4.2

CVE-2020-13882 json

CISOfy Lynis before 3.0.0 has Incorrect Access Control because of a TOCTOU race condition.

published 6y ago modified 4mo ago also EUVD-2020-6090

cvss
4.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 17%
public exploits
0
none known

Summary

CISOfy Lynis before 3.0.0 has Incorrect Access Control because of a TOCTOU race condition. The routine to check the log and report file permissions was not working as intended and could be bypassed locally. Because of the race, an unprivileged attacker can set up a log and report file, and control that up to the point where the specific routine is doing its check. After that, the file can be removed, recreated, and used for additional attacks.

Patch / fix

  • cisofy lynis 3.0.0
  • lynis Debian 14, Debian 13, Debian 12 3.0.0-1

debian advisories DEBIAN-CVE-2020-13882

  • lynis openSUSE Tumbleweed 3.0.5-3.2

opensuse advisories openSUSE-SU-2024:11032-1

Is CVE-2020-13882 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-13882 updated cvss 5.3

lynis: incorrect access control because of a TOCTOU race condition

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.2 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
NVD 2.0 3.7 AV:L/AC:H/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.