Skip to content

Conversation

@chait-slim
Copy link

No description provided.

shakedembo and others added 4 commits August 28, 2025 12:22
* Added following the existing directory structure a provider folder for rootio plus a provider class and a parser
* Added to the global cli config the rootio provider config mapping
* Added the rootio provider to the mapping in the global provider initialization
* Added the appropriate configuration for testing the new provider with a unit test

Signed-off-by: Shaked Dembo <[email protected]>
* Added root api for cve_feed as supported data sources
* Updated the output for vunnel list (noticed a drift with other ecosystems so I updated it to the latest)

Signed-off-by: Shaked Dembo <[email protected]>
  patched packages

  - Add ROOTIO_UNAFFECTED marker emission for packages with .root.io
  version suffix
  - Include vulnerable range constraint to exclude Root.io patched
  versions
  - Support both OS packages (Alpine, Debian, Ubuntu) and language
  packages (Python)
  - Add comprehensive unit tests for the parser modifications

  This prevents false positive vulnerability reports for packages that
  have been
  patched by Root.io security team.

Signed-off-by: Chai Tadmor <[email protected]>
if not fixed_versions:
cve_record["Vulnerability"]["FixedIn"].append({
"Name": package_name,
"Version": "", # Empty version indicates no fix available
Copy link
Contributor

Choose a reason for hiding this comment

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

I thought we had discussed at #863 (comment) that this vulnerability feed only supports records of fixes? Should this code ever be reachable?

namespace = data["Vulnerability"].get("NamespaceName", "")
if namespace == "rootio:language:python":
for fixed_in in data["Vulnerability"].get("FixedIn", []):
if fixed_in.get("Version") == "ROOTIO_UNAFFECTED":
Copy link
Contributor

Choose a reason for hiding this comment

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

Please don't use magic / sentinel values like this. You want the vunnel to emit an actual version at which the vulnerability was fixed.

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.

3 participants