[Aikido] Remove APIToken from CollectorConfig to prevent unauthenticated credential disclosure#81
Open
aikido-autofix[bot] wants to merge 1 commit into
Open
[Aikido] Remove APIToken from CollectorConfig to prevent unauthenticated credential disclosure#81aikido-autofix[bot] wants to merge 1 commit into
aikido-autofix[bot] wants to merge 1 commit into
Conversation
…prevent exposure of bearer tokens via the /sbom-collector/config endpoint.
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
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 patch addresses a critical security vulnerability where live bearer API tokens were being exposed through unauthenticated access to the /sbom-collector/config endpoint. The APIToken field has been removed from the CollectorConfig struct in pkg/models/collector_config.go and its population has been eliminated from the HandleGetCollectorConfig service method in internal/services/sbom/sbom.go. These changes ensure that sensitive authentication credentials are no longer transmitted in API responses, mitigating the risk of unauthorized API access through token disclosure.