Lucene search

K
symantecSymantec Security ResponseSMNTC-111300
HistoryDec 18, 2019 - 12:00 a.m.

Rack CVE-2019-16782 Information Disclosure Vulnerability

2019-12-1800:00:00
Symantec Security Response
www.symantec.com
10

Description

Rack is prone to an information-disclosure vulnerability. Attackers can exploit this issue to obtain sensitive information that may aid in further attacks.

Technologies Affected

  • Rack Project Rack 0.1
  • Rack Project Rack 0.2
  • Rack Project Rack 0.3
  • Rack Project Rack 0.4
  • Rack Project Rack 0.9.1
  • Rack Project Rack 1.0.0
  • Rack Project Rack 1.0.1
  • Rack Project Rack 1.1.0
  • Rack Project Rack 1.1.2
  • Rack Project Rack 1.1.3
  • Rack Project Rack 1.1.33
  • Rack Project Rack 1.1.4
  • Rack Project Rack 1.1.5
  • Rack Project Rack 1.1.6
  • Rack Project Rack 1.2.0
  • Rack Project Rack 1.2.1
  • Rack Project Rack 1.2.2
  • Rack Project Rack 1.2.3
  • Rack Project Rack 1.2.4
  • Rack Project Rack 1.2.6
  • Rack Project Rack 1.2.7
  • Rack Project Rack 1.3.0
  • Rack Project Rack 1.3.1
  • Rack Project Rack 1.3.10
  • Rack Project Rack 1.3.2
  • Rack Project Rack 1.3.3
  • Rack Project Rack 1.3.4
  • Rack Project Rack 1.3.5
  • Rack Project Rack 1.3.6
  • Rack Project Rack 1.3.7
  • Rack Project Rack 1.3.8
  • Rack Project Rack 1.3.9
  • Rack Project Rack 1.4.0
  • Rack Project Rack 1.4.1
  • Rack Project Rack 1.4.2
  • Rack Project Rack 1.4.3
  • Rack Project Rack 1.4.4
  • Rack Project Rack 1.4.5
  • Rack Project Rack 1.5.0
  • Rack Project Rack 1.5.1
  • Rack Project Rack 1.5.2
  • Rack Project Rack 1.6.0
  • Rack Project Rack 1.6.10
  • Rack Project Rack 1.6.11
  • Rack Project Rack 1.6.2
  • Rack Project Rack 1.6.5
  • Rack Project Rack 1.6.6
  • Rack Project Rack 1.6.7
  • Rack Project Rack 1.6.8
  • Rack Project Rack 1.6.9
  • Rack Project Rack 2.0.0
  • Rack Project Rack 2.0.1
  • Rack Project Rack 2.0.2
  • Rack Project Rack 2.0.3
  • Rack Project Rack 2.0.4
  • Rack Project Rack 2.0.5
  • Rack Project Rack 2.0.6
  • Rack Project Rack 2.0.7

Recommendations

Block external access at the network boundary, unless external parties require service.
If global access isn’t needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.

Run all software as a nonprivileged user with minimal access rights.
Running server processes within a restricted environment using facilities such as chroot or jail may limit the consequences of successful exploits.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.

Updates are available. Please see the references or vendor advisory for more information.