Vulnerabilities

A Vulnerability is a state in a computing system (or set of systems) which either (a) allows an attacker to execute commands as another user, (b) allows an attacker to access data that is contrary to the specified access restrictions for that data, (c) allows an attacker to pose as another entity, or (d) allows an attacker to conduct a denial of service.Advisories relating to Symantec products may be viewed here.

VMware Harbor Container Registry for PCF Multiple Security Vulnerabilities

Risk:
High
Date Discovered:
December 04, 2019
Description:
VMware Harbor Container Registry for PCF is prone to the following security vulnerabilities. 1. Multiple SQL-injection vulnerabilities 2. A cross-site request forgery vulnerability 3. A privilege-escalation vulnerability 4. A user-enumeration vulnerability Exploiting this issue could allow an attacker to compromise the application, access or modify data, exploit latent vulnerabilities in the underlying database, perform certain unauthorized actions and gain access to the affected application, gain elevated privileges, or harvest valid usernames. VMware Harbor Container Registry for PCF 1.8 through 1.8.5, and 1.9 through 1.9.2 are vulnerable.
Technologies Affected
  • VMWare Harbor Container Registry for PCF 1.8.0
  • VMWare Harbor Container Registry for PCF 1.8.1
  • VMWare Harbor Container Registry for PCF 1.8.2
  • VMWare Harbor Container Registry for PCF 1.8.3
  • VMWare Harbor Container Registry for PCF 1.8.5
  • VMWare Harbor Container Registry for PCF 1.9.0
  • VMWare Harbor Container Registry for PCF 1.9.2
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 a successful exploit.
  • Run all software as a nonprivileged user with minimal access rights.
    To limit the impact of a successful exploit, run server software with the least privileges required and in restricted environments while still maintaining functionality.
  • 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 unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.
  • Do not follow links provided by unknown or untrusted sources.
    Web users should be cautious about following links to websites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.
  • Set web browser security to disable the execution of JavaScript.
    Since exploiting cross-site scripting issues often requires the execution of malicious script code in web clients, consider disabling script code and active content support within a client browser as a way to prevent a successful exploit. Note that this mitigation tactic might adversely affect legitimate websites that rely on the execution of browser-based script code.
  • Implement multiple redundant layers of security.
    Implement measures such as '.htaccess' to provide an additional layer of authentication for sensitive or privileged information.
Updates are available. Please see the references or vendor advisory for more information.
References
Credits
Cure53
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

Disclaimer
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.