What is CVE-2015-9244?

CVE-2015-9244 is a medium-severity SQL injection vulnerability in mysql (npm), affecting versions <= 2.0.0-alpha7. It is fixed in 2.0.0-alpha8. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

Which versions of mysql are affected by CVE-2015-9244?

mysql (npm) versions <= 2.0.0-alpha7 is affected.

Is there a fix for CVE-2015-9244?

Yes. CVE-2015-9244 is fixed in 2.0.0-alpha8. Upgrade to this version or later.

Is CVE-2015-9244 exploitable, and should I be worried?

Whether CVE-2015-9244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2015-9244 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2015-9244?

Upgrade mysql to 2.0.0-alpha8 or later.

CVE-2015-9244 in mysql

Q: Which versions of mysql are affected by CVE-2015-9244?

mysql (npm) versions <= 2.0.0-alpha7 is affected.

Q: Is there a fix for CVE-2015-9244?

Yes. CVE-2015-9244 is fixed in 2.0.0-alpha8. Upgrade to this version or later.

Q: Is CVE-2015-9244 exploitable, and should I be worried?

Whether CVE-2015-9244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2015-9244 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2015-9244?

Upgrade mysql to 2.0.0-alpha8 or later.

Summary

SQL Injection in mysql

Versions of mysql prior to 2.0.0-alpha8 are affected by a SQL Injection vulnerability in the mysql.escape() function, which does not properly escape object keys.

Impact

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

Affected versions

mysql (<= 2.0.0-alpha7)

Security releases

mysql → 2.0.0-alpha8 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Update to version 2.0.0-alpha8 or later.

Frequently Asked Questions

What is CVE-2015-9244? CVE-2015-9244 is a medium-severity SQL injection vulnerability in mysql (npm), affecting versions <= 2.0.0-alpha7. It is fixed in 2.0.0-alpha8. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
Which versions of mysql are affected by CVE-2015-9244? mysql (npm) versions <= 2.0.0-alpha7 is affected.
Is there a fix for CVE-2015-9244? Yes. CVE-2015-9244 is fixed in 2.0.0-alpha8. Upgrade to this version or later.
Is CVE-2015-9244 exploitable, and should I be worried? Whether CVE-2015-9244 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2015-9244 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2015-9244? Upgrade mysql to 2.0.0-alpha8 or later.

Other vulnerabilities in mysql

CVE-IDSeverityPackage summary

CVE-2019-14939Mediummysql: MySQL for Node.js Unsafe Options GHSA-5F7M-MMPC-QHH4Mediummysql: mysql Node.JS Module Vulnerable to Remote Memory Exposure