-
Notifications
You must be signed in to change notification settings - Fork 88
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
Add Kubernetes ecosystem #319
Open
knqyf263
wants to merge
1
commit into
ossf:main
Choose a base branch
from
knqyf263:add_k8s
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,7 +8,7 @@ aside: | |
| show_edit_on_github: true | ||
| --- | ||
|
|
||
| **Version 1.6.7 (Sep 16, 2024)** | ||
| **Version 1.6.8 (Dec 4, 2024)** | ||
|
|
||
| Original authors: | ||
| - Oliver Chang ([email protected]) | ||
|
|
@@ -288,6 +288,17 @@ The defined database prefixes and their "home" databases are: | |
| </ul> | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>KUBE</code></td> | ||
| <td><a href="https://github.com/kubernetes-sigs/cve-feed-osv">Kubernetes Official CVE Feed</a></td> | ||
| <td> | ||
| <ul> | ||
| <li>How to contribute: <a href="https://github.com/kubernetes-sigs/cve-feed-osv/blob/main/CONTRIBUTING.md">https://github.com/kubernetes-sigs/cve-feed-osv/blob/main/CONTRIBUTING.md</a></li> | ||
| <li>Source URL: <code>https://kubernetes.io/docs/reference/issues-security/official-cve-feed/index.json</code></li> | ||
| <li>OSV Formatted URL: <code>https://raw.githubusercontent.com/kubernetes-sigs/cve-feed-osv/blob/main/vulns/<ID>.json</code></li> | ||
| </ul> | ||
| </td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>LBSEC</code></td> | ||
| <td><a href="https://github.com/loopbackio/security/tree/main/advisories">LoopBack Advisory Database</a></td> | ||
|
|
@@ -706,6 +717,7 @@ The defined ecosystems are: | |
| | `Go` | The Go ecosystem; the `name` field is a Go module path. | | ||
| | `Hackage` | The Haskell package ecosystem. The `name` field is a Haskell package name as published on Hackage. | | ||
| | `Hex` | The package manager for the Erlang ecosystem; the `name` is a Hex package name. | | ||
| | `Kubernetes` | The Kubernetes ecosystem; the `name` field is a Kubernetes component name. | | ||
| | `Linux` | The Linux kernel. The only supported `name` is `Kernel`. | | ||
| | `Mageia` | The Mageia Linux package ecosystem; the `name` is the name of the source package. The ecosystem string must have a `:<RELEASE-NUMBER>` suffix to scope the package to a particular Mageia release. Eg `Mageia:9`. | | ||
| | `Maven` | The Maven Java package ecosystem. The `name` field is a Maven package name in the format `groupId:artifactId`. The ecosystem string might optionally have a `:<REMOTE-REPO-URL>` suffix to denote the remote repository URL that best represents the source of truth for this package, without a trailing slash (e.g. `Maven:https://maven.google.com`). If this is omitted, this is assumed to be the Maven Central repository (`https://repo.maven.apache.org/maven2`). | | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there some documentation we can point to as an authoritative reference for what a component name is and how to format it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To clarify this comment a bit more using your example in kubernetes-sigs/cve-feed-osv#9 (comment):
It's unclear if the name should be "kube-apiserver", or "k8s.io/apiserver". Is there some clarification we can make here on the expected naming scheme?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @oliverchang, sorry for the late reply. I had been on vacation, and I've missed your comment in accumulated tasks.
Actually, I would like to discuss this point: I thought it would be difficult to distinguish
apiserverfrom non-upstream apiserver if we useapiserver, so I adapted it to Go's module name, likek8s.io/apiserverto clarify it's upstream, but it is not yet strictly defined. How can we distinguish between different flavors within the same ecosystem in the OSV schema?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have the convention of having a ":SUFFIX" qualifier for ecosystem names.
For example, for Debian:
Would something similar make sense for Kubernetes?
"Kubernetes" refers to upstream
"Kubernetes:
<distribution>" refers to a specific distribution?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sounds reasonable. Should we define a list of
<distribution>here? It seems difficult to list all the K8s distributions, so can we simply show an example, like“Kubernetes:<distribution>”, e.g. “Kubernetes:GKE”or something like that?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should define them, at least for the ones where we know there is a vulnerability database published. OSV's goal is to make vulnerability advisories machine readable and consistent.