November 15, 2019
Multiple Kubernetes Sidecar Containers are prone to an unauthorized access vulnerability. An attacker can exploit this issue to gain unauthorized access and perform unintended actions. This may lead to further attacks.
- Kubernetes external-provisioner 0.4.1
- Kubernetes external-provisioner 0.4.2
- Kubernetes external-provisioner 1.0.0
- Kubernetes external-provisioner 1.0.1
- Kubernetes external-provisioner 1.1.0
- Kubernetes external-provisioner 1.2.1
- Kubernetes external-provisioner 1.3.0
- Kubernetes external-resizer 0.1.0
- Kubernetes external-resizer 0.2.0
- Kubernetes external-snapshotter 0.4.0
- Kubernetes external-snapshotter 0.4.1
- Kubernetes external-snapshotter 1.0.0
- Kubernetes external-snapshotter 1.0.1
- Kubernetes external-snapshotter 1.1.0
- Kubernetes external-snapshotter 1.2.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.
Execute all software as a user with minimal privileges. Use additional precautions such as restrictive environments to insulate software that may potentially handle malicious content.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review logs regularly.
Updates are available. Please see the references or vendor advisory for more information.
The vendor reported this issue.
© 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.