CVE-2017-10910 json
Denial of Service in mqtt
published 8y ago modified 4mo ago also GHSA-h9mj-fghc-664w , EUVD-2017-0363
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
MQTT.js 2.x.x prior to 2.15.0 issue in handling PUBLISH tickets may lead to an attacker causing a denial-of-service condition.
Patch / fix
- npm mqtt 2.15.0
- mqtt.js_project mqtt.js 2.15.0
Is CVE-2017-10910 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 FencerExploit prediction
2.26% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:N/A:P |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | mqtt | >=2.0.0, <2.15.0 |
2.15.0 |
Affected products
- MQTT.js. MQTT.js
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
References
-
github.com
/mqttjs/MQTT.js/commit/403ba53b838f2d319a0c0505a045fe00239e9923
web, patch, third-party-advisory
-
jvn.jp
/en/jp/JVN45494523/index.html
third-party-advisory, web, vdb-entry
-
github.com
/mqttjs/MQTT.js/releases/tag/v2.15.0
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2017-10910
advisory
-
github.com
/advisories/GHSA-h9mj-fghc-664w
advisory
-
github.com
/mqttjs/MQTT.js
package
-
github.com
/nodejs/security-wg/blob/master/vuln/npm/357.json
web
-
npmjs.com
/advisories/555
web
Sources
- CVE List CVE-2017-10910
- GitHub Advisory GHSA-h9mj-fghc-664w
- NVD CVE-2017-10910
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.