Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

GHSA-5f7m-mmpc-qhh4 — mysql

Fix: mysqljs/mysql@192fe45

GHSA-5f7m-mmpc-qhh4 is a security vulnerability in mysql. A fix is available for mysql — see the affected versions and patch details below.

mysql Node.JS Module Vulnerable to Remote Memory Exposure

Published
May 23, 2019
Updated
Aug 3, 2022
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 3, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

8Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
mysqlnpm
919Kdownloads / week

Description

Versions of mysql before 2.14.0 are vulnerable to remove memory exposure.

Affected versions of mysql package allocate and send an uninitialized memory over the network when a number is provided as a password.

Only mysql running on Node.js versions below 6.0.0 are affected due to a throw added in newer node.js versions.

Proof of Concept:

require('mysql').createConnection({
  host: 'localhost',
  user: 'user',
  password : USERPROVIDEDINPUT,  // number
  database : 'my_db'
}).connect();

Recommendation

Update to version 2.14.0 or later.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmmysql≥ 2.0.0-alpha8&&< 2.14.02.14.0npm install mysql@2.14.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update mysql to 2.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5f7m-mmpc-qhh4 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-5f7m-mmpc-qhh4 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-5f7m-mmpc-qhh4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `mysql` before 2.14.0 are vulnerable to remove memory exposure. Affected versions of `mysql` package allocate and send an uninitialized memory over the network when a number is provided as a password. Only `mysql` running on Node.js versions below 6.0.0 are affected due to a throw added in newer node.js versions. Proof of Concept: ``` require('mysql').createConnection({ host: 'localhost', user: 'user', password : USERPROVIDEDINPUT, // number database : 'my_db' }).connect(); ``` ## Recommendation Update to version 2.14.0 or later.
O3 Security · Impact-Aware SCA

Is GHSA-5f7m-mmpc-qhh4 in your dependencies?

O3 Security finds GHSA-5f7m-mmpc-qhh4 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-5f7m-mmpc-qhh4: mysql | O3 Security