October 22, 2019
Cloud Foundry SMB Volume is prone to an information disclosure vulnerability. An attacker can exploit this issue to gain access to sensitive information; this may lead to further attacks.
- Cloud Foundry SMB Volume 1.0.0
- Cloud Foundry SMB Volume 1.1.0
- Cloud Foundry SMB Volume 1.2.0
- Cloud Foundry SMB Volume 1.3.0
- Cloud Foundry SMB Volume 2.0.0
- Cloud Foundry SMB Volume 2.0.1
- Cloud Foundry SMB Volume 2.0.2
- Cloud Foundry cf-deployment 0.35.0
- Cloud Foundry cf-deployment 0.36.0
- Cloud Foundry cf-deployment 10.0.0
- Cloud Foundry cf-deployment 10.1.0
- Cloud Foundry cf-deployment 11.0.0
- Cloud Foundry cf-deployment 11.1.0
- Cloud Foundry cf-deployment 7.3.0
- Cloud Foundry cf-deployment 7.4.0
- Cloud Foundry cf-deployment 7.5.0
- Cloud Foundry cf-deployment 7.6.0
- Cloud Foundry cf-deployment 7.7.0
- Cloud Foundry cf-deployment 7.8.0
- Cloud Foundry cf-deployment 7.9.0
- Cloud Foundry cf-deployment 9.0.0
- Cloud Foundry cf-deployment 9.1.0
- Cloud Foundry cf-deployment 9.2.0
- Cloud Foundry cf-deployment 9.3.0
- Cloud Foundry cf-deployment 9.4.0
- Cloud Foundry cf-deployment 9.5.0
- Pivotal Application Service 2.5.0
- Pivotal Application Service 2.5.1
- Pivotal Application Service 2.5.10
- Pivotal Application Service 2.5.11
- Pivotal Application Service 2.5.2
- Pivotal Application Service 2.5.3
- Pivotal Application Service 2.5.4
- Pivotal Application Service 2.5.5
- Pivotal Application Service 2.5.6
- Pivotal Application Service 2.5.7
- Pivotal Application Service 2.5.8
- Pivotal Application Service 2.5.9
- Pivotal Application Service 2.6.0
- Pivotal Application Service 2.6.2
- Pivotal Application Service 2.6.3
- Pivotal Application Service 2.6.5
- Pivotal Application Service 2.6.7
- Pivotal Application Service 2.7.0
- Pivotal Application Service 2.7.1
- Pivotal Isolation Segment 2.5.0
- Pivotal Isolation Segment 2.5.1
- Pivotal Isolation Segment 2.5.2
- Pivotal Isolation Segment 2.5.3
- Pivotal Isolation Segment 2.5.4
- Pivotal Isolation Segment 2.5.5
- Pivotal Isolation Segment 2.5.6
- Pivotal Isolation Segment 2.5.7
- Pivotal Isolation Segment 2.5.8
- Pivotal Isolation Segment 2.5.9
- Pivotal Isolation Segment 2.6.0
- Pivotal Isolation Segment 2.6.3
- Pivotal Isolation Segment 2.6.6
- Pivotal Isolation Segment 2.7.0
- Pivotal Isolation Segment 2.7.1
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.
Communicate sensitive information over encrypted channels.
Ensure that only encrypted channels are used for communicating sensitive information.
Updates are available. Please see the references or vendor advisory for more information.
Cloud Foundry Foundation Security Team
© 1995- 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 firstname.lastname@example.org.
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 email@example.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.