Quick answers
- Is CVE-2022-3978 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-3978 being exploited in the wild.
- How severe is CVE-2022-3978?
- Low severity, with a CVSS score of 3.1, published 13 November 2022.
- Which products and versions are affected?
- NodeBB up to 2.5.7.
- Is there a fix for CVE-2022-3978?
- A patch was published on 2022-11-09: Fixed in NodeBB v2.5.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-3978 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2022-3978?
- Check whether you run NodeBB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Cross-Site Request Forgery (CWE-352) vulnerability was discovered in the `/register/abort` endpoint of NodeBB up to version 2.5.7. The endpoint, which terminates user registration sessions, did not validate CSRF tokens on POST requests, allowing attackers to construct forged requests triggered by visiting a malicious website. An attacker could craft a page that, when visited by a user in an active registration flow, would automatically submit a request to abort their registration without their knowledge. The attack requires network access and user interaction (visiting a malicious page), but no authentication. The vulnerability was patched in version 2.5.8 by adding CSRF token validation to the endpoint and updating the registration completion template to include the token in abort requests (commit 2f9d8c3).
Affected products
- NodeBB NodeBB up to 2.5.7
Identifiers
- CVE-2022-3978
- GHSA-5gwx-wf9g-r5mx
Timeline
- 2022-11-13: disclosed: Vulnerability published in OSV
- 2022-11-09: patched: Fixed in NodeBB v2.5.8