CVE-2015-7330
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 · uneditedPuppet Enterprise 2015.3 before 2015.3.1 allows remote attackers to bypass a host whitelist protection mechanism by leveraging the Puppet communications protocol.
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 2015.3 versions prior to 2015.3.1 contain a security flaw where remote attackers can bypass host whitelist protection mechanisms by manipulating the Puppet communications protocol. The whitelist, intended to restrict which hosts can participate in Puppet communications, can be circumvented through protocol-level manipulation.
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= 2015.3.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Identify Puppet Enterprise installation and versionRun `puppet --version` or check the Puppet Enterprise version file typically at `/etc/puppetlabs/puppet/version` to determine if Puppet Enterprise is installed and its exact version numberAffected if The installed version is exactly 2015.3.0 (not later versions)
-
Confirm the product is Puppet EnterpriseCheck for Puppet Enterprise-specific directories or files such as `/etc/puppetlabs/pe-puppet` or run `facter is_pe` to confirm the installation is Puppet Enterprise rather than open-source PuppetAffected if The system is running Puppet Enterprise 2015.3.0 specifically
-
Verify whitelist authorization is configuredExamine the Puppet authorization configuration file at `/etc/puppetlabs/puppet/auth.conf` or the classifier configuration to determine if a whitelist for node requests is definedAffected if A whitelist mechanism (such as `auth_whitelist` or certificate name restrictions) is actively configured in the Puppet Enterprise environment
-
Inspect Puppet communications configurationReview the Puppet master and agent configuration files in `/etc/puppetlabs/puppet/puppet.conf` for any host restriction settings or examine the console/classifier whitelist settings under the PE Console node classifierAffected if Host whitelist protections are in place but the version is vulnerable 2015.3.0
A system is affected if it runs Puppet Enterprise version 2015.3.0 specifically and has whitelist-based host restrictions configured to control Puppet communications participation.
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 dataUpgrade Puppet Enterprise to version 2015.3.1 or later to obtain the patch for this whitelist bypass vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7330 — 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-7330 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