How severe is GHSA-5f7m-mmpc-qhh4?

No CVSS score has been assigned to GHSA-5f7m-mmpc-qhh4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5f7m-mmpc-qhh4?

GHSA-5f7m-mmpc-qhh4 affects the following packages: mysql (npm). Ecosystems affected: npm.

How do I fix GHSA-5f7m-mmpc-qhh4?

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.

How do I detect GHSA-5f7m-mmpc-qhh4 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5f7m-mmpc-qhh4 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-5f7m-mmpc-qhh4?

O3 pinpoints whether GHSA-5f7m-mmpc-qhh4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5f7m-mmpc-qhh4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5f7m-mmpc-qhh4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-5f7m-mmpc-qhh4 published, and has it been updated?

GHSA-5f7m-mmpc-qhh4 was published on May 23, 2019 and was last updated on August 3, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-5f7m-mmpc-qhh4

GHSA-5f7m-mmpc-qhh4 is a security vulnerability in mysql. O3 Security confirms whether GHSA-5f7m-mmpc-qhh4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Blast Radius

1 pkg affected

📦mysql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mysql`	≥ 2.0.0-alpha8&&< 2.14.0	2.14.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mysql. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-5f7m-mmpc-qhh4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 detects GHSA-5f7m-mmpc-qhh4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works