Skip to content

Fix Bitnami CPE application part - #5127

Draft
vigneshakaviki wants to merge 1 commit into
anchore:mainfrom
vigneshakaviki:agent/fix-bitnami-cpe-application-part
Draft

Fix Bitnami CPE application part#5127
vigneshakaviki wants to merge 1 commit into
anchore:mainfrom
vigneshakaviki:agent/fix-bitnami-cpe-application-part

Conversation

@vigneshakaviki

Copy link
Copy Markdown

Description

Bitnami SPDX SBOMs can declare CPEs with a wildcard part even though the
discovered components are applications. Syft preserved that wildcard, producing
less-specific CPEs such as:

cpe:2.3:*:rabbitmq-cluster-operator:rabbitmq-cluster-operator:2.16.1:*:*:*:*:*:*:*

This change normalizes wildcard parts to the CPE application part when importing
Bitnami packages:

cpe:2.3:a:rabbitmq-cluster-operator:rabbitmq-cluster-operator:2.16.1:*:*:*:*:*:*:*

Existing Bitnami cataloger expectations now cover the normalized part.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I have added unit tests that cover changed behavior
  • I have tested my code in common scenarios and confirmed there are no regressions
  • I have added comments to my code, particularly in hard-to-understand sections

Testing

  • make lint
  • make unit
  • make integration
  • Reproduced against bitnamilegacy/rabbitmq-cluster-operator:2.16.1-debian-12-r0

Issue references

Fixes #5123

Signed-off-by: vigneshakaviki <kumarvignesh295@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CPE identifiers contain a wildcard in the CPE part field for packages discovered by the Bitnami cataloger.

1 participant