CVE-2015-8470
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 · uneditedThe console in Puppet Enterprise 3.7.x, 3.8.x, and 2015.2.x does not set the secure flag for the JSESSIONID cookie in an HTTPS session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an HTTP session.
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 · high confidenceThe Puppet Enterprise console fails to set the 'secure' flag on the JSESSIONID cookie during HTTPS sessions. Without this flag, browsers may transmit the session cookie over insecure HTTP connections, enabling attackers on the network path to intercept and hijack user sessions.
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>= 3.7.0, <= 3.7.2>= 3.8.0, <= 3.8.6>= 2015.2.0, <= 2015.2.3CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Identify Puppet Enterprise versionRun `puppet --version` or check the PE version file at `/opt/puppetlabs/puppet/var/state/enterprise_version`Affected if The installed version falls within 3.7.0-3.7.2, 3.8.0-3.8.6, or 2015.2.0-2015.2.3
-
Verify HTTPS is enabled for the consoleCheck the console configuration file (typically in `/etc/puppetlabs/console-services/conf.d/` or inspect the console-ssl configuration) for HTTPS/SSL settingsAffected if HTTPS is enabled and the console is accessible over HTTPS
-
Inspect JSESSIONID cookie configurationAccess the Puppet Enterprise console over HTTPS using a browser, open developer tools (F12), go to the Application/Storage tab, find the JSESSIONID cookie, and examine its attributes. Alternatively, check the underlying application server (typically Tomcat) configuration for the session cookie settings in the relevant context XML or server configuration filesAffected if The JSESSIONID cookie exists but does NOT have the 'Secure' flag set, meaning it could be transmitted over HTTP
A user is affected if they run a vulnerable Puppet Enterprise version (3.7.x, 3.8.x, or 2015.2.x within the specified ranges) with HTTPS enabled but the JSESSIONID cookie lacks the Secure flag, allowing potential session hijacking over insecure connections.
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.
From vendor dataConfigure the application server or web server underlying the Puppet Enterprise console to set the 'Secure' attribute on the JSESSIONID cookie, ensuring the browser only transmits it over encrypted HTTPS connections.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8470 — 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-2015-8470 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