Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-22745: Buffer Overlow in TSS2_RC_Decode in tpm2-tss

Noroxi assessment

Priority: Monitor (action score 25/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.53% (FIRST EPSS).
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: tpm2-tss (AlmaLinux:8) 2.3.2-5.el8; tpm2-tss-devel (AlmaLinux:8) 2.3.2-5.el8; tpm2-tss (AlmaLinux:9) 3.2.2-2.el9.

Low priority for now. Upgrade to tpm2-tss (AlmaLinux:8) 2.3.2-5.el8; tpm2-tss-devel (AlmaLinux:8) 2.3.2-5.el8; tpm2-tss (AlmaLinux:9) 3.2.2-2.el9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

tpm2-tss is an open source software implementation of the Trusted Computing Group (TCG) Trusted Platform Module (TPM) 2 Software Stack (TSS2). In versions prior to 4.1.0-rc0, 4.0.1, and 3.2.2-rc1, `Tss2_RC_SetHandler` and `Tss2_RC_Decode` both index into `layer_handler` with an 8 bit layer number, but the array only has `TPM2_ERROR_TSS2_RC_LAYER_COUNT` entries, so trying to add a handler for higher-numbered layers or decode a response code with such a layer number reads/writes past the end of the buffer. This Buffer overrun, could result in arbitrary code execution. An example attack would be a MiTM bus attack that returns 0xFFFFFFFF for the RC. Given the common use case of TPM modules an attacker must have local access to the target machine with local system privileges which allows access to the TPM system. Usually TPM access requires administrative privilege. Versions 4.1.0-rc0, 4.0.1, and 3.2.2-rc1 fix the issue.

MediumCVSS 6.4 · v3.1—No exploit Fix available
Published
Jan 19, 2023
Updated
Jun 17, 2026
EPSS
0.5% · 45th percentile

Report tools

JSON

Action score

25

Monitor

Low priority for now.

CVSS
25 / 40 · 6.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.4
CNA · GitHub_M
6.4
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-22745

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
tpm2 software stack projecttpm2 software stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • tpm2 software stack project tpm2 software stackbefore 3.2.2
  • tpm2 software stack project tpm2 software stack4.0.0 and later · before 4.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • tpm2-software tpm2-tss

    • < 4.0.1, < 3.2.2-rc0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8tpm2-tssbefore 2.3.2-5.el82.3.2-5.el8
AlmaLinux:8tpm2-tss-develbefore 2.3.2-5.el82.3.2-5.el8
AlmaLinux:9tpm2-tssbefore 3.2.2-2.el93.2.2-2.el9
AlmaLinux:9tpm2-tss-develbefore 3.2.2-2.el93.2.2-2.el9
Debian:12tpm2-tssbefore 3.2.1-33.2.1-3
openSUSE:Leap 15.4tpm2-0-tssbefore 2.4.5-150300.3.6.12.4.5-150300.3.6.1
openSUSE:Leap Micro 5.3tpm2-0-tssbefore 3.1.0-150400.3.3.13.1.0-150400.3.3.1
Red Hat:enterprise_linux:8::baseostpm2-tssbefore 0:2.3.2-5.el80:2.3.2-5.el8
Red Hat:enterprise_linux:8::baseostpm2-tss-debuginfobefore 0:2.3.2-5.el80:2.3.2-5.el8
Red Hat:enterprise_linux:8::baseostpm2-tss-debugsourcebefore 0:2.3.2-5.el80:2.3.2-5.el8
Red Hat:enterprise_linux:8::baseostpm2-tss-develbefore 0:2.3.2-5.el80:2.3.2-5.el8
Red Hat:enterprise_linux:9::baseostpm2-tssbefore 0:3.2.2-2.el90:3.2.2-2.el9
Red Hat:enterprise_linux:9::baseostpm2-tss-debuginfobefore 0:3.2.2-2.el90:3.2.2-2.el9
Red Hat:enterprise_linux:9::baseostpm2-tss-debugsourcebefore 0:3.2.2-2.el90:3.2.2-2.el9
Red Hat:enterprise_linux:9::crbtpm2-tss-develbefore 0:3.2.2-2.el90:3.2.2-2.el9
Red Hat:rhel_aus:8.6::baseostpm2-tssbefore 0:2.3.2-5.el8_60:2.3.2-5.el8_6
Red Hat:rhel_aus:8.6::baseostpm2-tss-debuginfobefore 0:2.3.2-5.el8_60:2.3.2-5.el8_6
Red Hat:rhel_aus:8.6::baseostpm2-tss-debugsourcebefore 0:2.3.2-5.el8_60:2.3.2-5.el8_6
Red Hat:rhel_aus:8.6::baseostpm2-tss-develbefore 0:2.3.2-5.el8_60:2.3.2-5.el8_6
Red Hat:rhel_eus:8.8::baseostpm2-tssbefore 0:2.3.2-5.el8_80:2.3.2-5.el8_8
Red Hat:rhel_eus:8.8::baseostpm2-tss-debuginfobefore 0:2.3.2-5.el8_80:2.3.2-5.el8_8
Red Hat:rhel_eus:8.8::baseostpm2-tss-debugsourcebefore 0:2.3.2-5.el8_80:2.3.2-5.el8_8
Red Hat:rhel_eus:8.8::baseostpm2-tss-develbefore 0:2.3.2-5.el8_80:2.3.2-5.el8_8
SUSE:Linux Enterprise Micro 5.3tpm2-0-tssbefore 3.1.0-150400.3.3.13.1.0-150400.3.3.1

+1

Other highest-scoring records for the same primary product.

  • CVE-2020-24455Missing initialization of a variable in the TPM2 source may allow a privileged user to potentially enable an escalation of privilege via loc
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:tpm2-tss3.2.2-2.el9 · AlmaLinux:9Package registry (OSV)
almalinux:tpm2-tss-devel3.2.2-2.el9 · AlmaLinux:9Package registry (OSV)
debian:tpm2-tss3.2.1-3 · Debian:12Package registry (OSV)
opensuse:tpm2-0-tss3.1.0-150400.3.3.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
red hat:tpm2-tss0:3.2.2-2.el9 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:tpm2-tss-debuginfo0:3.2.2-2.el9 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:tpm2-tss-debugsource0:3.2.2-2.el9 · Red Hat:enterprise_linux:9::baseosPackage registry (OSV)
red hat:tpm2-tss-devel0:3.2.2-2.el9 · Red Hat:enterprise_linux:9::crbPackage registry (OSV)
suse:tpm2-0-tss3.1.0-150400.3.3.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
char buf[256];memcpy(buf, pkt->data, pkt->len);

Fixed

c
char buf[256];if (pkt->len > sizeof(buf)) {  return -EINVAL;}memcpy(buf, pkt->data, pkt->len);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records