Kubernetes vulnerability dashboard

Question

Kubernetes vulnerability dashboard

tallclair opened this issue 5 years ago · 21 comments

Should we have a central place where kubernetes security vulnerabilities are published? Our current announcement template includes a lot of mailing lists, and discuss.kubernetes.io. We also usually file a github issue with more details on the vulnerability.

Some ideas include:

(current process) just use kubernetes-security-announce history
Create a security bulletin on the website (something similar to GKE security bulletins or AWS security bulletins)
Use github
- File github issues with a dedicated label
- File github issues in a dedicated repo
- Leverage GitHub security advisories?

/help

sbs2001 commented 3 years ago

/reopen

Answer 1 · 2019-11-14T21:46:14.000Z

@tallclair:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

Should we have a central place where kubernetes security vulnerabilities are published? Our current announcement template includes a lot of mailing lists, and discuss.kubernetes.io. We also usually file a github issue with more details on the vulnerability.

Some ideas include:

(current process) just use kubernetes-security-announce history

Create a security bulletin on the website (something similar to GKE security bulletins or AWS security bulletins)

Use github

File github issues with a dedicated label

File github issues in a dedicated repo

Leverage GitHub security advisories?

/help

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.

Answer 2 · 2019-12-02T19:29:07.000Z

A few notes on github security advisories:

Require repo admin privileges to create
I think advisories cannot be edited or amended once published
There is an atom feed (and API) associated with a repo's security advisories, so they could suffice as a dashboard & feed

Answer 3 · 2020-03-01T19:59:14.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Answer 4 · 2020-03-03T00:13:55.000Z

/remove-lifecycle stale

Answer 5 · 2020-06-01T00:37:47.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Answer 6 · 2020-07-01T01:19:30.000Z

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

Answer 7 · 2020-07-08T00:53:39.000Z

/remove-lifecycle rotten

Answer 8 · 2020-07-24T21:37:47.000Z

/cc @justaugustus

An approach to a vulnerability dashboard that we discussed: add a new kind/cve label, and ensure that CVE patches get a release note along the lines of kubernetes/kubernetes#92941:

CVE-2020-8559 (Medium): Privilege escalation from compromised node to cluster. See kubernetes/kubernetes#92914 for more details.

Then, leverage https://relnotes.k8s.io/ filtered by kind/cve as the vulnerability dashboard.

Answer 9 · 2020-10-22T21:40:28.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Answer 10 · 2020-10-23T14:40:01.000Z

I'd like to either:

hyperlink to that content from https://k8s.io/
transclude the same content into a page on https://k8s.io/

Answer 11 · 2020-10-29T17:04:46.000Z

/remove-lifecycle stale

Answer 12 · 2021-01-27T17:30:16.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

Answer 13 · 2021-02-26T18:16:24.000Z

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

Answer 14 · 2021-03-28T19:02:35.000Z

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Answer 15 · 2021-03-28T19:02:44.000Z

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/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.

Answer 16 · 2021-12-09T04:15:00.000Z

/remove-lifecycle stale

Answer 17 · 2021-12-09T04:15:38.000Z

@sbs2001: Reopened this issue.

In response to this:

/reopen

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.

Answer 18 · 2021-12-09T04:28:54.000Z

An alternative approach would be to do something like Istio project does. Eg they have markdown documents with embedded yaml like this. Then these are rendered by frontend like this .

IMHO the advantage of this approach is that users can know whether they are affected and how to fix the issue all in one page.

FWIW I've been converting the security announcements to yaml format as part of ismyk8ssecure. See advisories in particular. It contains the CVE and a list of versions of the particular kubernetes component which is vulnerable to it. Adding the fixes to these documents will be trivial. Using these documents creating a bulletin would be fairly easy.

Answer 19 · 2022-01-08T05:24:34.000Z

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue or PR with /reopen
Mark this issue or PR as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Answer 20 · 2022-01-08T05:24:55.000Z

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue or PR with /reopen

Mark this issue or PR as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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.