CVE Intelligence
Skip to main content
MEDIUM

CVE-2023-5309

CVE-2023-5309 — Broken Session Management in Puppet Enterprise

Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations.

Published Updated Sources: cvelistV5, Perforce

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

0%

chance of exploitation in 30 days

Affects

puppet

puppet_enterprise

CVSS base

6.8

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

puppet

Products (1)

puppet enterprise

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
6.8CVSS 3.1MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-384

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1134.002Access Token Manipulation: Create Process with Token
  • T1134.003Access Token Manipulation: Make and Impersonate Token
  • T1606Forge Web Credentials

References

1 on the record

Elsewhere on this site

  • puppetevery CVE for this vendor
  • CWE-384other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.