# CVE-2015-9244: SQL Injection in mysql

> Attackers can execute arbitrary SQL commands via unescaped object keys in the mysql Node.js module, potentially compromising database integrity and confidentiality.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 29 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2015-9244, GHSA-fvq6-55gv-jx9f

## What is CVE-2015-9244?

CVE-2015-9244 is a critical SQL injection vulnerability in HackerOne mysql node module, published on 29 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Keys of objects in mysql node module v2.0.0-alpha7 and earlier are not escaped with `mysql.escape()` which could lead to SQL Injection.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

2 open source packages ship an affected version, including mysql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mysql` | npm | All versions | 2.0.0-alpha8 |
| `mysql` | npm | All versions | 2.0.0-alpha8 |

Products: Mysqljs Mysql.

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

Upgrade mysql to 2.0.0-alpha8 or later.

## Is CVE-2015-9244 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-9244 is a critical SQL injection vulnerability in HackerOne mysql node module, published on 29 May 2018. 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-9244 in the wild and no public exploit code.

Affected packages and fixed versions:
- mysql (npm): affected all versions; fixed in 2.0.0-alpha8
- mysql (npm): affected all versions; fixed in 2.0.0-alpha8

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-9244/ (Markdown: https://insights.sbomify.com/CVE-2015-9244/index.md)
```

## Sources

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

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