Null Byte Interaction Error (Poison Null Byte) Affecting rubygem-io-console package, versions <0:0.4.2-36.el7


Severity

Recommended
medium

Based on CentOS security rating.

Threat Intelligence

EPSS
0.38% (74th 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 IDSNYK-CENTOS7-RUBYGEMIOCONSOLE-2137265
  • published26 Jul 2021
  • disclosed28 Mar 2018

Introduced: 28 Mar 2018

CVE-2018-8779  (opens in a new tab)
CWE-626  (opens in a new tab)

How to fix?

Upgrade Centos:7 rubygem-io-console to version 0:0.4.2-36.el7 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rubygem-io-console package and not the rubygem-io-console package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

In Ruby before 2.2.10, 2.3.x before 2.3.7, 2.4.x before 2.4.4, 2.5.x before 2.5.1, and 2.6.0-preview1, the UNIXServer.open and UNIXSocket.open methods are not checked for null characters. It may be connected to an unintended socket.