CVE-2023-5309
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVersions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePuppet Enterprise versions prior to 2021.7.6 and 2023.5 contain a session management flaw in SAML implementations that can be exploited to bypass authentication or hijack user sessions, leading to critical unauthorized access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2021.7.6>= 2023.0, < 2023.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Puppet Enterprise versionRun `puppetserver --version` or check the Puppet Enterprise console UI footer for the version number, or inspect the version file typically at /opt/puppetlabs/puppetserver/versions.confAffected if Version is below 2021.7.6, or is 2023.0.x through 2023.4.x
-
Verify SAML authentication is configuredLog into the Puppet Enterprise console and navigate to Authentication settings, or check for SAML IdP configuration in /etc/puppetlabs/enterprise/conf.d or via ` puppetserver ` command if SAML authentication backend is enabledAffected if SAML single sign-on is enabled as an authentication method
-
Confirm SAML session configuration existsCheck for SAML-related configuration files in /opt/puppetlabs/puppetserver/services or review the console RBAC settings for SAML identity provider (IdP) entriesAffected if SAML IdP metadata is loaded and active in the PE authentication chain
User is affected if Puppet Enterprise version falls in the vulnerable ranges AND SAML authentication is actively configured/enabled in their environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2021.7.62023.5.0
Upgrade Puppet Enterprise to version 2021.7.6 or 2023.5 or later to resolve the broken SAML session management.
Puppet Enterprise 2023.5.0 (or 2021.7.6 for 2021.x branches)
- Upgrade Puppet Enterprise to version 2023.5.0 or later for installations running 2023.x
- Upgrade Puppet Enterprise to version 2021.7.6 or later for installations running 2021.x
- Consult Puppet Enterprise documentation for upgrade procedures specific to your deployment model
- After upgrade, verify SAML authentication is functioning correctly
- Review session management settings in Puppet console post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5309 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5309 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data