Skip to content
Fencer Intel
high 7.1

CVE-2020-28407 json

In swtpm before 0.4.2 and 0.5.x before 0.5.1, a local attacker may be able to overwrite arbitrary files via a symlink attack against a temp…

published 3y ago modified 4mo ago also EUVD-2020-20866

cvss
7.1
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 20%
public exploits
0
none known

Summary

In swtpm before 0.4.2 and 0.5.x before 0.5.1, a local attacker may be able to overwrite arbitrary files via a symlink attack against a temporary file such as TMP2-00.permall.

Patch / fix

  • swtpm_project swtpm 0.4.2
  • swtpm openSUSE Tumbleweed 0.6.1-1.1

opensuse advisories openSUSE-SU-2024:11416-1

  • swtpm Arch Linux 0.5.1-1

arch linux advisories AVG-1282

Is CVE-2020-28407 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-28407 updated cvss 7.3

swtpm: symlink issue may lead to privilege escalation

  • Red Hat Enterprise Linux 8 Advanced Virtualization swtpm, swtpm-libs, swtpm-tools, swtpm-tools-pkcs11
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 8 Advanced Virtualization swtpm, swtpm-libs, swtpm-tools, swtpm-tools-pkcs11 Red Hat Enterprise Linux 9 swtpm, swtpm-libs, swtpm-tools
    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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.