Skip to content

vuln: CVE-2022-32214 was fixed in 16.16.0, not 16.20.0 - #1591

Closed
wwang-vc wants to merge 1 commit into
nodejs:mainfrom
wwang-vc:fix-cve-2022-32214-patched
Closed

wwang-vc wants to merge 1 commit into
nodejs:mainfrom
wwang-vc:fix-cve-2022-32214-patched

Conversation

@wwang-vc

Copy link
Copy Markdown

vuln/core/95.json gives the patched 16.x version of CVE-2022-32214 as ^16.20.0. The July 2022 security release post fixed it in v14.20.0, v16.16.0 and v18.5.0. The file was added on 2022-07-08 (#809), before 16.20.0 existed (March 2023), so 16.20.0 looks like a typo for 16.16.0. The 14.x and 18.x versions already match the post.

As written, any tool reading the file reports 16.16.0–16.19.x as vulnerable to CVE-2022-32214.

Only 95.json changes. I've left vuln/core/index.json and the OpenVEX file for the update workflows to regenerate.

🤖 Generated with Claude Code

The July 2022 security release fixed CVE-2022-32214 in v14.20.0, v16.16.0
and v18.5.0. vuln/core/95.json was added on 2022-07-08 with 16.20.0 for
the 16.x line, a version released only in March 2023.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants