Skip to content

Add the acceptance of cwes field to the GrypeEntry#905

Merged
jormundur00 merged 1 commit intomasterfrom
jormundur00/gh-904
Dec 19, 2025
Merged

Add the acceptance of cwes field to the GrypeEntry#905
jormundur00 merged 1 commit intomasterfrom
jormundur00/gh-904

Conversation

@jormundur00
Copy link
Copy Markdown
Member

What does this PR do?

Currently, GrypeTask fails for some docker images due to a missing cwes field. In this PR, we add the missing field to the GrypeEntry class, so it is properly ignored.

Fixes: #904

@jormundur00 jormundur00 self-assigned this Dec 19, 2025
@jormundur00 jormundur00 added bug Something isn't working docker Pull requests that update docker code labels Dec 19, 2025
}

class Cwe {
public String cve;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that map the CWE (Common Weakness Enumerator, ~= vulnerability type) to an individual CVE (actual vulnaerability) in the json?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, exactly. An example of an Cwe object looks like the following: CWE(cve=CVE-2022-2879, cwe=CWE-770, type=Primary).

We currently don't use this specific field in our analysis, but must register (and ignore) it so our parsing of the Grype output doesn't fail.

@jormundur00 jormundur00 merged commit 628c9dc into master Dec 19, 2025
28 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working docker Pull requests that update docker code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: checkAllowedDockerImages task fails due to incomplete GrypeEntry class

2 participants