Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2020-8568: Secrets sync/rotate directory traversal #378

Closed
tam7t opened this issue Nov 10, 2020 · 2 comments
Closed

CVE-2020-8568: Secrets sync/rotate directory traversal #378

tam7t opened this issue Nov 10, 2020 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@tam7t
Copy link
Contributor

tam7t commented Nov 10, 2020

CVSS Rating: Medium(5.8) CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N

Modification of SecretProviderClassPodStatus/Status resource could result in writing content to the host filesystem and syncing file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that contain other Kubernetes Secrets.

Am I vulnerable?

The attacker must have permissions to update or patch the secretproviderclasspodstatuses/status resources which is not granted by default and the auto rotations feature must be enabled which is also not enabled by default.

Affected Versions

v0.0.16
v0.0.15

How do I mitigate this vulnerability?

Do not grant users or workloads permissions to modify secretproviderclasspodstatuses/status resources. Upgrade the driver to v0.0.17 or above which include additional verifications on the targetPath field.

Fixed Versions

v0.0.17 - fixed by #371

Detection

N/A

@tam7t tam7t added the kind/bug Categorizes issue or PR as related to a bug. label Nov 10, 2020
@aramase aramase pinned this issue Nov 10, 2020
@aramase
Copy link
Member

aramase commented Nov 14, 2020

This CVE has been fixed with v0.0.17 release of the driver.

/close

@aramase aramase unpinned this issue Nov 14, 2020
@k8s-ci-robot
Copy link
Contributor

@aramase: Closing this issue.

In response to this:

This CVE has been fixed with v0.0.17 release of the driver.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants