CVE-2015-7224
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 · uneditedpuppetlabs-mysql 3.1.0 through 3.6.0 allow remote attackers to bypass authentication by leveraging creation of a database account without a password when a 'mysql_user' user parameter contains a host with a netmask.
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 puppetlabs-mysql module versions 3.1.0 through 3.6.0 contain a vulnerability where database accounts are created without passwords when the 'mysql_user' resource host parameter contains a netmask notation (e.g., '192.168.1.0/24'). This allows remote attackers to bypass authentication and gain unauthorized database 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>= 3.1.0, <= 3.6.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.0/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.
-
Identify puppetlabs-mysql module versionRun 'puppet module list' or inspect the module's metadata.json file in the Puppet modulepath to determine the installed version of the puppetlabs-mysql module.Affected if The installed version is 3.1.0 through 3.6.0 inclusive
-
Locate mysql_user resources using netmask host notationSearch Puppet manifests and Hiera data for 'mysql_user' resource declarations. Examine the 'host' parameter value for CIDR netmask notation such as '192.168.1.0/24' or '10.0.0.0/8'.Affected if Any mysql_user resource uses a netmask in the host parameter (for example: '192.168.1.0/24', '10.0.0.0/8')
-
Verify password configuration for netmask-based usersReview the mysql_user resource definitions to check whether the 'password' parameter is explicitly set for users with netmask host values.Affected if The password parameter is missing, empty, or not explicitly set for mysql_user resources using netmask notation in the host parameter
A system is affected if the puppetlabs-mysql module version is between 3.1.0 and 3.6.0 and mysql_user resources are defined with netmask host notation without explicit password configuration.
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 · scopedUpdate puppetlabs-mysql module to version 3.6.1 or later and audit all mysql_user resources using netmask notation in host parameters to ensure proper password assignment and account configuration.
Upgrade puppetlabs-mysql module to version 3.7.0 or later
- Identify all Puppet nodes using the puppetlabs-mysql module versions 3.1.0 through 3.6.0
- Review your mysql_user resource definitions to identify any that use a host parameter with a netmask (e.g., '192.168.1.0/24')
- Upgrade the puppetlabs-mysql module to the latest available version beyond 3.6.0
- After upgrading, test all mysql_user resources to ensure passwords are properly set for users with netmask hosts
- Verify that authentication works correctly for all database accounts created with host-based netmasks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.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,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7224 — 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-7224 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