CVE-2019-11243

In Kubernetes v1.12.0-v1.12.4 and v1.13.0, the rest.AnonymousClientConfig() method returns a copy of the provided config, with credentials removed (bearer token, username/password, and client certificate/key data). In the affected versions, rest.AnonymousClientConfig() did not effectively clear service account credentials loaded using rest.InClusterConfig()

Weakness

The product does not drop privileges before passing control of a resource to an actor that does not have those privileges.

Affected Software

Potential Mitigations

• Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

• http://www.securityfocus.com/bid/108053
• https://github.com/kubernetes/kubernetes/issues/76797
• https://security.netapp.com/advisory/ntap-20190509-0002/
• http://www.securityfocus.com/bid/108053
• https://github.com/kubernetes/kubernetes/issues/76797
• https://security.netapp.com/advisory/ntap-20190509-0002/