# CVE-2015-7224: Auth bypass in n/a

> Remote attackers can bypass authentication in Puppet MySQL module by exploiting netmask handling in user parameters to create passwordless database accounts.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Dec 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-7224, GHSA-cg6c-24mc-jmx8

## What is CVE-2015-7224?

CVE-2015-7224 is a critical authentication bypass vulnerability in n/a, published on 21 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

puppetlabs-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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2015-7224?

It affects 1 product.


Products: Puppet Puppetlabs-Mysql.

## How do I fix CVE-2015-7224?

Upgrade to a fixed version.

## Is CVE-2015-7224 being exploited?

There is no known exploitation of CVE-2015-7224 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-3276](https://insights.sbomify.com/CVE-2022-3276/): Puppetlabs-mysql Command Injection (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7224 and fix it if it is affected.

What it is: CVE-2015-7224 is a critical authentication bypass vulnerability in n/a, published on 21 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-7224 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-7224/ (Markdown: https://insights.sbomify.com/CVE-2015-7224/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-7224
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-7224
- OSV: https://osv.dev/vulnerability/CVE-2015-7224

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-7224/
Summaries are generated and may contain mistakes; the official description above is the record.