Skip to content
Fencer Vulns
high 7.8

CVE-2017-16837 json

Certain function pointers in Trusted Boot (tboot) through 1.9.6 are not validated and can cause arbitrary code execution, which allows loca…

published 2017-11-16 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-8011

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

Certain function pointers in Trusted Boot (tboot) through 1.9.6 are not validated and can cause arbitrary code execution, which allows local users to overwrite dynamic PCRs of Trusted Platform Module (TPM) by hooking these function pointers.

Patch / fix

  • tboot Ubuntu 20.04 LTS 1.9.7-0ubuntu1

ubuntu advisories UBUNTU-CVE-2017-16837

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • tboot SLES for SAP 12 SP3, SLES for SAP 12 SP2, SLES 12 SP3 +1 more 20160518_1.9.4-7.5.1

suse advisories SUSE-SU-2017:3090-1

  • tboot openSUSE Tumbleweed 20210614_1.10.2-2.2

opensuse advisories openSUSE-SU-2024:11424-1

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-2017-16837 updated cvss 5.5

tboot: Incorrect validation of certain function pointers

  • Red Hat Enterprise Linux 6 tboot Red Hat Enterprise Linux 7 tboot
    affected: no fix planned “Will not fix”

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.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns 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.