CVE-2022-36045 json
Account takeover via cryptographically weak PRNG in NodeBB Forum
published 4y ago modified 4mo ago also GHSA-p4cc-w597-6cpm , EUVD-2022-6591
- cvss
- 9.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. It utilizes web sockets for instant interactions and real-time notifications. `utils.generateUUID`, a helper function available in essentially all versions of NodeBB (as far back as v1.0.1 and potentially earlier) used a cryptographically insecure Pseudo-random number generator (`Math.random()`), which meant that a specially crafted script combined with multiple invocations of the password reset functionality could enable an attacker to correctly calculate the reset code for an account they do not have access to. This vulnerability impacts all installations of NodeBB. The vulnerability allows for an attacker to take over any account without the involvement of the victim, and as such, the remediation should be applied immediately (either via NodeBB upgrade or cherry-pick of the specific changeset. The vulnerability has been patched in version 2.x and 1.19.x. There is no known workaround, but the patch sets listed above will fully patch the vulnerability.
Patch / fix
- npm nodebb 1.19.8, 2.0.1
- nodebb nodebb 1.19.8
Is CVE-2022-36045 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nodebb | <1.19.8 >=2.0.0, <2.0.1 |
1.19.8 2.0.1 |
Affected products
- NodeBB NodeBB
Classification
References
-
github.com
/NodeBB/NodeBB/commit/81e3c1ba488d03371a5ce8d0ebb5c5803026e0f9
web, patch, third-party-advisory
-
github.com
/NodeBB/NodeBB/commit/e802fab87f94a13f397f04cfe6068f2f7ddf7888
web, patch, third-party-advisory
-
github.com
/NodeBB/NodeBB/security/advisories/GHSA-p4cc-w597-6cpm
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-36045
advisory
-
github.com
/NodeBB/NodeBB
package
Sources
- CVE List CVE-2022-36045
- GitHub Advisory GHSA-p4cc-w597-6cpm
- NVD CVE-2022-36045
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.