CVE-2024-383557.3HighCWE-754

CVE-2024-38355: Unhandled 'error' event in socket.io

socketio · socket.io

Affected: socketio socket.io · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.8%probability of exploitation in the next 30 days

57th percentile

050100

Higher than 57% of scored CVEs

7.3HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

Socket.IO is an open source, real-time, bidirectional, event-based, communication framework. A specially crafted Socket.IO packet can trigger an uncaught exception on the Socket.IO server, thus killing the Node.js process. This issue is fixed by commit `15af22fc22` which has been included in `socket.io@4.6.2` (released in May 2023). The fix was backported in the 2.x branch as well with commit `d30630ba10`. Users are advised to upgrade. Users unable to upgrade may attach a listener for the "error" event to catch these errors.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

socketio · socket.io< 2.5.1; >= 3.0.0,< 4.6.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Check for Unusual or Exceptional Conditions · Input Validation and Logic
Vendor: socketio
Published: June 2024
Band: Unlikely (under 1%), June 2024

CoverageNo articles yet

No CyberSIXT article names CVE-2024-38355 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.