Correctly annotate affected package #5990
Merged
Conversation
This file contains hidden or 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 vulnerability was incorrectly edited by GitHub staff without consulting the project and has now resulted in incorrect reports propagating downstream. As noted in the original report, this affects the rotation endpoints on the server; it does not impact the client API package. See also: GHSA-prpj-rchp-9j5h Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
This was referenced Aug 12, 2025
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Resolves: golang#3877 Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Resolves: golang#3877 Signed-off-by: Alexander Scheel <ascheel@gitlab.com>
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Resolves: golang#3877 Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Resolves: golang#3877 Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Resolves: golang#3877 Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
cipherboy
added a commit
to cipherboy/golang-vulndb
that referenced
this pull request
Aug 12, 2025
This vulnerability was incorrectly edited by GitHub staff without consulting the project. As noted in the original report, this affects the rotation endpoints on the server: it does not impact the client API package in any way. This vulnerability was original to HashiCorp Vault thus the initial affected version is 0 (present in all earlier OpenBao versions). The server is not directly importable and should not be consumed by third-parties except through a release. See also: GHSA-prpj-rchp-9j5h See also: github/advisory-database#5990 Fixes: golang#3877 Signed-off-by: Alexander Scheel <alexander.m.scheel@gmail.com>
|
Hi @cipherboy, Apologies for the error and thanks for the correction 🙇. 2.3.1 is not uploaded to the Go registry. In these cases, we include the fixed Go pseudo-version (0.0.0-20250625150133-fe75468822a2) as well. |
|
@JonathanLEvans OpenBao's server is not meant to be imported by other Go modules so it isn't typically published in that manner (currently it is blocked by the registry by using a v2 version tag on a v1 module). I think that's why we opted to do a non-Go ecosystem at first (Package The only real way to consume this module is through a release build of the server binary (such as from upstream or manually rebuilding it yourself). Thoughts? Should I remove the Go |
|
@cipherboy Your distribution method makes sense. However, there is nothing stopping users may use the Go packaging system to import openbao so we want a global advisory to tell them whether the version they are using is affected if they do. We would want a global advisory regardless what you put as the package name in your repo advisory. |
1b20754
into
github:cipherboy/advisory-improvement-5990
2 checks passed
|
Hi @cipherboy! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This vulnerability was incorrectly edited by GitHub staff without consulting the project and has now resulted in incorrect reports propagating downstream.
As noted in the original report, this affects the rotation endpoints on the server; it does not impact the client API package.
See also: GHSA-prpj-rchp-9j5h