Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Range is missing its upper bound even though it's defined in GHSA #474

Closed
nscuro opened this issue Jun 30, 2022 · 2 comments
Closed

Range is missing its upper bound even though it's defined in GHSA #474

nscuro opened this issue Jun 30, 2022 · 2 comments

Comments

@nscuro
Copy link

nscuro commented Jun 30, 2022

I came across the guava vulnerability GHSA-5mg8-w23w-74h3 (https://osv.dev/vulnerability/GHSA-5mg8-w23w-74h3) for which GHSA declares the affected version range as <= 29.0.

In OSV, this is represented as:

"ranges": [
    {
        "type": "ECOSYSTEM",
        "events": [
            {
                "introduced": "0"
            }
        ]
    }
],
"database_specific": {
    "last_known_affected_version_range": "<= 29.0"
}

Given the constraint <= 29.0, I would've expected the following:

"ranges": [
    {
        "type": "ECOSYSTEM",
        "events": [
            {
                "introduced": "0"
            },
            {
                "last_affected": "29.0"
            }
        ]
    }
]

The range currently advertised by OSV will raise lots of false positives, considering the latest guava version is 31.1.

@oliverchang
Copy link
Collaborator

Thanks for filing this! Could you please raise this issue in https://github.com/github/advisory-database ? We are getting the GHSA OSV entry from there and they currently do not yet support last_affected.

@nscuro
Copy link
Author

nscuro commented Jul 1, 2022

@oliverchang Thanks for the pointer, I'll raise an issue in the GHSA repo later today. 👌🏻

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

No branches or pull requests

2 participants