Skip to content

Feathers socket handler allows abusing implicit toString

High severity GitHub Reviewed Published Jul 19, 2023 in feathersjs/feathers • Updated Nov 7, 2023

Package

npm @feathersjs/socketio (npm)

Affected versions

<= 4.5.17
>= 5.0.0, <= 5.0.7

Patched versions

4.5.18
5.0.8
npm @feathersjs/transport-commons (npm)
<= 4.5.17
>= 5.0.0, <= 5.0.7
4.5.18
5.0.8

Description

Impact

Feathers socket handler did not catch invalid string conversion errors like:

const message = `${{ toString: '' }}`

Causing the NodeJS process to crash when sending an unexpected Socket.io message like

socket.emit('find', { toString: '' })

Patches

A fix has been released in

  • v5.0.8 via #3241
  • v4.5.18 via #3242

Workarounds

Since it is in the core Socket handling code upgrading to the latest version is necessary.

References

References

@daffl daffl published to feathersjs/feathers Jul 19, 2023
Published by the National Vulnerability Database Jul 19, 2023
Published to the GitHub Advisory Database Jul 20, 2023
Reviewed Jul 20, 2023
Last updated Nov 7, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(42nd percentile)

Weaknesses

Improper Check for Unusual or Exceptional Conditions

The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. Learn more on MITRE.

CVE ID

CVE-2023-37899

GHSA ID

GHSA-hhr9-rh25-hvf9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.