google / google/deps.dev

All `flatbuffers` PyPI Versions Display as Vulnerable (False Positive)

Open
#107 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Go
Stars
443
Forks
54
Avg merge
1d 22h
Merged PRs (30d)
3

Description

On deps.dev, every version of the [flatbuffers](https://deps.dev/pypi/flatbuffers) PyPI package displays as vulnerable with the same set of OSVs. Looking into the OSVs further, all vulnerabilities were introduced and patched in 2021 (e.g: [OSV-2021-1229](https://osv.dev/vulnerability/OSV-2021-1229)). On deps.dev however, [it shows](https://deps.dev/advisory/osv/OSV-2021-1229) this OSV impacts all versions of `flatbuffers`.

I believe this is a false positive, and if I had to guess I would say it's happening because the **Affected Version** and **Fixed** metadata fields on the OSV use commit SHAs instead of package versions, and deps.dev cannot map commits to versions. The same applies to all other OSVs affecting this package.

Running [trivy](https://github.com/aquasecurity/trivy) and [osv-scanner](https://github.com/google/osv-scanner) on a repository using the `flatbuffers` PyPI at any version does not flag `flatbuffers` as vulnerable.

I am reaching out because these OSVs are causing the prominent [tensorflow package](https://deps.dev/pypi/tensorflow/) on deps.dev to appear vulnerable at every version although I believe it is not. Any help in dismissing these advisories on deps.dev or clarifying the behavior here would be helpful.

Here's the [OSV-2021-1229 YAML file](https://github.com/google/oss-fuzz-vulns/blob/main/vulns/flatbuffers/OSV-2021-1229.yaml); this is one of several OSVs for flatbuffers. Notably, the YAML only contains commit SHAs, not package versions.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.