mysql Node.JS Module Vulnerable to Remote Memory Exposure

published 2019-05-23 7y ago modified 2022-08-03 4y ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

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.

Patch / fix

fixed in 1 links 2

npm mysql 2.14.0

github.com/mysqljs/mysql@192fe45 commit
github.com/mysqljs/mysql@310c6a7 commit

Is GHSA-5f7m-mmpc-qhh4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem	package	affected	fixed in
npm	mysql	>=2.0.0-alpha8, <2.14.0	2.14.0

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

GitHub Advisory GHSA-5f7m-mmpc-qhh4

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.