Out-of-Bounds Affecting cube-1.6 package, versions *


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
2.02% (79th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Out-of-Bounds vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-CUBE16-16719980
  • published17 May 2026
  • disclosed31 May 2018

Introduced: 31 May 2018

CVE-2016-10518  (opens in a new tab)
CWE-119  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest cube-1.6.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cube-1.6 package and not the cube-1.6 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

A vulnerability was found in the ping functionality of the ws module before 1.0.0 which allowed clients to allocate memory by sending a ping frame. The ping functionality by default responds with a pong frame and the previously given payload of the ping frame. This is exactly what you expect, but internally ws always transforms all data that we need to send to a Buffer instance and that is where the vulnerability existed. ws didn't do any checks for the type of data it was sending. With buffers in node when you allocate it when a number instead of a string it will allocate the amount of bytes.