← 返回列表

CVE-2020-8561

单站 Kubernetes Vulnerability Announcements 发布 Wed, 01 Sep 2021 20:18:50 +0000 入库 2026-11-18T06:56:49

Repository navigation

area/security

cve/wontfixIndicates that an announced CVE does not require a fix.Indicates that an announced CVE does not require a fix.

kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.

lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.

official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)

sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.

triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.

Description

on Sep 1, 2021

A security issue was discovered in Kubernetes where actors that control the responses of MutatingWebhookConfiguration or ValidatingWebhookConfiguration requests are able to redirect kube-apiserver requests to private networks of the apiserver. If that user can view kube-apiserver logs when the log level is set to 10, they can view the redirected responses and headers in the logs.

This issue has been rated Medium (https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N) (4.1), and assigned CVE-2020-8561

Am I vulnerable?

You may be vulnerable if --profiling is enabled on the kube-apiserver and actors who control a validating or mutating webhook can access the kube-apiserver process logs.

Affected Versions

This issue affects all known versions of kube-apiserver.

How do I mitigate this vulnerability?

This issue can be mitigated by not allowing kube-apiserver access to sensitive resources or networks, or to reduce the “-v” flag value to less than 10 and set the “--profiling” flag value to “false” (default value is “true”). Setting the profiling flag to “false” prevents users from dynamically modifying the kube-apiserver log level, and the flag value Webhook requests may still be redirected to private networks with a log level less than 10, but the response body will not be logged.

Fixed Versions

There is no fix for this issue at this time.

Detection

Examining kube-apiserver log responses is the only known method of detection for this issue.

If you find evidence that this vulnerability has been exploited, please contact security@kubernetes.io

Acknowledgements

This vulnerability was reported by QiQi Xu

/triage accepted

/lifecycle frozen

/area security

/kind bug

/committee security-response

Activity

  1. micahhausleradded kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.on Sep 1, 2021
  2. k8s-ci-robotadded lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.on Sep 1, 2021
  3. k8s-ci-robot commentedon Sep 1, 2021 ContributorMore actions @micahhausler: The label(s) committee/security-response cannot be applied, because the repository doesn't have them.

Details In response to this:

/triage accepted
/lifecycle frozen
/area security
/kind bug
/committee security-response
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.
4. k8s-ci-robotadded triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.Indicates an issue or PR lacks a `sig/foo` label and requires one.on Sep 1, 2021
5. micahhauslerchanged the title ~~[-]TITLE: PLACEHOLDER ISSUE[/-]~~ [+]PLACEHOLDER ISSUE[/+] on Sep 1, 2021
6. micahhauslerchanged the title ~~[-]PLACEHOLDER ISSUE[/-]~~ [+]CVE-2020-8561: Webhook redirect in kube-apiserver[/+] on Sep 15, 2021
7. ### neolit123 commentedon Sep 20, 2021 MemberMore actions /sig api-machinery instrumentation
8. k8s-ci-robotadded sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.sig/instrumentationCategorizes an issue or PR as relevant to SIG Instrumentation.Categorizes an issue or PR as relevant to SIG Instrumentation. and removed needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.Indicates an issue or PR lacks a `sig/foo` label and requires one.on Sep 20, 2021
9. ### k8s-triage-robot commentedon Feb 8, 2023 More actions This issue has not been updated in over 1 year, and should be re-triaged. You can:
- Confirm that this issue is still relevant with /triage accepted (org members only)
- Close this issue with /close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
10. k8s-ci-robotadded needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.on Feb 8, 2023
11. ### 14 remaining items
12. ### k8s-triage-robot commentedon Jun 28, 2024 More actions This issue has not been updated in over 1 year, and should be re-triaged. You can:
- Confirm that this issue is still relevant with /triage accepted (org members only)
- Close this issue with /close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
13. k8s-ci-robotadded needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.on Jun 28, 2024
14. ### BenTheElder commentedon Jul 2, 2024 MemberMore actions /triage accepted
15. k8s-ci-robotadded triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on. and removed needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.on Jul 2, 2024
16. ### konryd commentedon Oct 30, 2024 ContributorMore actions I'm not seeing here the option to have apiserver reject following redirects (either all of them, or following some sort of same-origin policy). Was this considered?
17. ### sherine-k commentedon Sep 1, 2025 More actions /label official-cve-feed
18. ### k8s-ci-robot commentedon Sep 1, 2025 ContributorMore actions @sherine-k: Can not set label official-cve-feed: Must be member in one of these teams: [security-response-committee]

Details In response to this:

/label official-cve-feed 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-sigs/prow repository.
19. ### cji commentedon Sep 29, 2025 MemberMore actions /label official-cve-feed
20. k8s-ci-robotadded official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)on Sep 29, 2025
21. ### tabbysable commentedon Jun 1, 2026 MemberMore actions Today I have updated the CVE record for this vulnerability to more-accurately reflect that all versions are affected. Please see the blog post for further information.
/label cve/wontfix
/close
22. k8s-ci-robotadded cve/wontfixIndicates that an announced CVE does not require a fix.Indicates that an announced CVE does not require a fix.on Jun 1, 2026
23. k8s-ci-robotclosed this as completedon Jun 1, 2026
24. ### k8s-ci-robot commentedon Jun 1, 2026 ContributorMore actions @tabbysable: Closing this issue.

Details In response to this:

Today I have updated the CVE record for this vulnerability to more-accurately reflect that all versions are affected. Please see the blog post for further information.
/label cve/wontfix
/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-sigs/prow repository.

Metadata

Metadata

Assignees

Labels

area/security

cve/wontfixIndicates that an announced CVE does not require a fix.Indicates that an announced CVE does not require a fix.

kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.

lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.

official-cve-feedIssues or PRs related to CVEs officially announced by Security Response Committee (SRC)Issues or PRs related to CVEs officially announced by Security Response Committee (SRC)

sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.

triage/acceptedIndicates an issue or PR is ready to be actively worked on.Indicates an issue or PR is ready to be actively worked on.

原文链接:https://github.com/kubernetes/kubernetes/issues/104720