Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8567PUBLISHED: 2021-01-21Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.
CVE-2020-8568PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that conta...
CVE-2020-8569PUBLISHED: 2021-01-21
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when:
- The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass.
- The snapshot-controller crashes, ...
CVE-2020-8570PUBLISHED: 2021-01-21
Kubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executi...
CVE-2020-8554PUBLISHED: 2021-01-21
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typicall...
User Rank: Author
10/30/2019 | 4:59:47 PM
Security and its many disciplines are tough jobs. You're usually an overhead function, which means constant budget pressure, especially if you don't have a clear risk management process/plan. Security leaders have a difficult time navigating what the relationship with the board should be (and thier responsibilties), leaving the security team in ambiguous states of responsibility - a bad place ot be in a breach. Every company today is tehcnolgy driven, and tech adoption and operationalization is often the lynchpin of competitive edge... agile security is hard and can drag the business in it's goals.
I think there's some organizational coaching work, better leadership around roles and repsonsibilties, and better technical approaches that could change the climate for the security proffessional.