Skip to content

Add Root IO provider labels for cassandra test image#167

Open
chait-slim wants to merge 2 commits intoanchore:mainfrom
chait-slim:rootio-labels
Open

Add Root IO provider labels for cassandra test image#167
chait-slim wants to merge 2 commits intoanchore:mainfrom
chait-slim:rootio-labels

Conversation

@chait-slim
Copy link

@chait-slim chait-slim commented Dec 30, 2025

Added vulnerability match labels for Root IO provider validation:

  • Image: docker.io/rootpublic/cassandra:latest@sha256:02272b14efbe14e70ee5512ce707c4e300d3c1813f0e5df9562512c1b96be835
  • 4 labels created for standard Ubuntu packages
  • Root IO packages correctly show 0 matches (NAK pattern working)

These labels are required for the Root IO provider PR in vunnel.

@willmurphyscode
Copy link
Contributor

Hi @chait-slim I am unable to pull the test image:

❯ docker pull cr.root.io/cassandra@sha256:b3cc918a6a364af0a6b0a45becef0d0979db7e604751fad627ec2a94945b4e03
Error response from daemon: failed to resolve reference "cr.root.io/cassandra@sha256:b3cc918a6a364af0a6b0a45becef0d0979db7e604751fad627ec2a94945b4e03": pull access denied, repository does not exist or may require authorization: authorization failed: no basic auth credentials

Am I missing something? Is it possible for you all to make an old tag public or something?

@chait-slim
Copy link
Author

Hi @chait-slim I am unable to pull the test image:

❯ docker pull cr.root.io/cassandra@sha256:b3cc918a6a364af0a6b0a45becef0d0979db7e604751fad627ec2a94945b4e03
Error response from daemon: failed to resolve reference "cr.root.io/cassandra@sha256:b3cc918a6a364af0a6b0a45becef0d0979db7e604751fad627ec2a94945b4e03": pull access denied, repository does not exist or may require authorization: authorization failed: no basic auth credentials

Am I missing something? Is it possible for you all to make an old tag public or something?

Updated the image location: docker.io/rootpublic/cassandra:latest@sha256:02272b14efbe14e70ee5512ce707c4e300d3c1813f0e5df9562512c1b96be835

Updated vulnerability match labels for Root IO provider validation:
- Image: docker.io/rootpublic/cassandra:latest@sha256:02272b14efbe14e70ee5512ce707c4e300d3c1813f0e5df9562512c1b96be835
- 4 labels created for standard Ubuntu packages
- Scanned with grype@0.104.0 (database built 2026-01-15)

These labels are required for the Root IO provider PR in vunnel.

Signed-off-by: Chai Tadmor <chai.tadmor@root.io>
@willmurphyscode
Copy link
Contributor

Hi @chait-slim can you add some labels that are FPs? As I understand the current plan is for the rootio provider to emit UnaffectedPackageHandles that prevent Grype from matching on vulnerabilities that Root has patched. When compared with a scan by Grype that doesn't know about rootio patches, this would be a False Positive. In other words, for the labels to prove that the approach is working, there should be matches that Grype finds without the rootio data, that it stops finding with the rootio data, that are labeled as False Positives, that is, as matches that it is correct for Grype to stop finding.

@chait-slim
Copy link
Author

@willmurphyscode I've added another image that should have better labels

@willmurphyscode
Copy link
Contributor

@chait-slim I'm confused. All of the labels in this branch have "label": "TP" in them. But when we're building a provider that works via NAKs / unaffectedPackageHandles, we need some false positives, that should have "label": "FP" in the JSON.

@willmurphyscode
Copy link
Contributor

Hi @chait-slim just wanted to make sure we are not both waiting on each other. My understanding is that I am waiting for you to push some changes to this PR showing that some of grype's current findings against RootIO should be labeled "FP" (false positive) but everything still has "TP" labels in this PR.

Please let me know if there's anything I can do to help.

@chait-slim
Copy link
Author

chait-slim commented Mar 9, 2026 via email

@chait-slim
Copy link
Author

chait-slim commented Mar 10, 2026

@willmurphyscode updated
Added FP labels for CVE-2016-20013 (libc-bin, libc6, locales) and CVE-2021-46848 (libtasn1-6) on both the cassandra and ubuntu rootpublic images.
These are vulnerabilities Root IO has patched — grype correctly suppresses them with the custom-db via unaffectedPackageHandles, so they should be
labeled FP, not left unlabeled.

    CVE-2016-20013 (libc-bin, libc6, locales) and CVE-2021-46848 (libtasn1-6)
    are patched by Root IO; grype[custom-db] correctly suppresses them via
    unaffectedPackageHandles. Labels these as FP so the quality gate can
    distinguish intentional suppressions from unlabeled unknowns.

Signed-off-by: Chai Tadmor <chai.tadmor@root.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants