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.

Sign up for GitHub

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

Jump to bottom

Semver metavuln #2804

Closed
Adam-Ignjatovic opened this issue Jun 26, 2023 · 1 comment
Closed

Semver metavuln #2804

Adam-Ignjatovic opened this issue Jun 26, 2023 · 1 comment

Comments

@Adam-Ignjatovic
Copy link

Adam-Ignjatovic commented Jun 26, 2023 •
edited
Loading

Please bump your semver version.
@ljharb
Copy link
Member

ljharb commented Jun 26, 2023

Like most CVEs, it's a false positive. We're not using new Range nor are we doing anything that wouldn't be a self-attack (ie, not an attack).

We can't ever bump the semver version because v7 drops support for engines we support, so unless the fix is backported to v6, it'll just have to remain a false positive.

Duplicate of #2803.

@ljharb ljharb closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2023
This was referenced Jun 26, 2023
Closed
Closed
Closed
Closed
Closed
Closed
@SukkaW SukkaW mentioned this issue Jul 3, 2023
Merged
This was referenced Jul 3, 2023
Closed
Closed
Closed
Closed
Closed
@ljharb ljharb mentioned this issue Jul 13, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ljharb @Adam-Ignjatovic