Engine.IO prior 3.6.1/6.2.1 HTTP Request uncaught exception
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Engine.IO. The affected element is an unknown function of the component HTTP Request Handler. Such manipulation leads to uncaught exception. This vulnerability is traded as CVE-2022-41940. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Engine.IO. It has been rated as problematic. Affected by this issue is an unknown part of the component HTTP Request Handler. The manipulation with an unknown input leads to a uncaught exception vulnerability. Using CWE to declare the problem leads to CWE-248. An exception is thrown from a function, but it is not caught. Impacted is availability. CVE summarizes:
Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the engine.io package, including those who uses depending packages like socket.io. There is no known workaround except upgrading to a safe version. There are patches for this issue released in versions 3.6.1 and 6.2.1.
The weakness was shared 11/22/2022 as GHSA-r7qp-cfhv-p84w. The advisory is available at github.com. This vulnerability is handled as CVE-2022-41940 since 09/30/2022. The technical details are unknown and an exploit is not available.
Upgrading to version 3.6.1 or 6.2.1 eliminates this vulnerability. Applying the patch 425e833ab13373edf1dd5a0706f07100db14e3c6 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 7.1
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Uncaught exceptionCWE: CWE-248
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Engine.IO 3.6.1/6.2.1
Patch: 425e833ab13373edf1dd5a0706f07100db14e3c6
Timeline
09/30/2022 🔍11/22/2022 🔍
11/22/2022 🔍
12/21/2022 🔍
Sources
Advisory: GHSA-r7qp-cfhv-p84wStatus: Confirmed
CVE: CVE-2022-41940 (🔍)
GCVE (CVE): GCVE-0-2022-41940
GCVE (VulDB): GCVE-100-214154
Entry
Created: 11/22/2022 07:41Updated: 12/21/2022 18:53
Changes: 11/22/2022 07:41 (40), 12/21/2022 18:53 (21)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.