Skip to content

Remove the overly broad match from GHSA to limit scanner noise. #930

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

Merged
merged 1 commit into from
Jun 12, 2025

Conversation

calebbrown
Copy link
Contributor

The GitHub repo github.com/primefaces/primereact-sass-theme uses a package.json file for this name squatting attack and has a version 10.8.5.

The overly broad version range from GitHub that covers every version means that this repo is matched and if someone has the repo checked out it will be potentially considered malicious by a scanning tool.

This change leaves the original version range from @awsactran.

The GitHub repo github.com/primefaces/primereact-sass-theme uses a
package.json file for this name squatting attack and has a version 10.8.5.

The overly broad version range from GitHub that covers every version means
that this repo is matched and if someone has it repo checked out it
will be potentially considered malicious.

Signed-off-by: Caleb Brown <calebbrown@google.com>
@calebbrown calebbrown requested review from 6mile and elitsa-gosst June 12, 2025 00:55
@calebbrown calebbrown merged commit f765ad5 into main Jun 12, 2025
9 checks passed
@calebbrown calebbrown deleted the primereact-sass-theme branch June 12, 2025 01:00
@awsactran
Copy link
Contributor

This behavior seems to be happening for awhile from Github, and some other IIRC. Do you think this will need a quick campaign to address this in the repo?

According to some conversations I have seen, the main reason they did this probably because of an assumption that once a package turned malicious, none of any other versions should be trusted.

My quick script shows there seems to be at least hundreds of packages being tagged with version 0.

@calebbrown
Copy link
Contributor Author

I think it is fine for now. Most of the time there aren't any issues, but occasionally someone does have problems.

I'd prefer that GitHub had more accurate version ranges, but I don't think they have the resources to do that.

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