How many CVEs have patched setResponseHeaders?

2 published CVEs changed setResponseHeaders in vercel/next.js, in 2 distinct patches totalling 8 changed lines, between 2021 and 2022.

What is the latest CVE that changed setResponseHeaders?

CVE-2022-23646 (Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0), published 2022-02-17, changed lines 566 to 580 of packages/next/server/image-optimizer.ts.

How does setResponseHeaders compare to the rest of vercel/next.js?

vercel/next.js has 39 CVEs with a located fix in total; 2 of them changed setResponseHeaders.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

vercel/next.js

Function

setResponseHeaders

Name: setResponseHeaders in vercel/next.js: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

packages/next/server/image-optimizer.ts

Last patched February 17, 2022

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

8

Lines changed

Added plus removed

2021–2022

Years

By CVE publication date

Overview

setResponseHeaders in vercel/next.js was changed by 2 published CVE fixes between 2021 and 2022, in 2 distinct patches that added or removed 8 lines in total.

vercel/next.js has 39 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed setResponseHeaders, newest first, with the lines each fix touched.

Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0
CVE-2022-23646 · lines 566–580 · +2 −4
High · CVSS 7.5
EPSS 1.8%2022-02-17
XSS in Image Optimization API for Next.js
CVE-2021-39178 · lines 528–529 · +2 −0
High · CVSS 7.5
EPSS 1.1%2021-08-30

Get an alert when the next CVE fix lands in vercel/next.js, with the patched functions.

Monitor next.js CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in vercel/next.js changed by the most CVE fixes.

createRedirectRenderResult2 CVEs · packages/next/src/server/app-render/action-handler.ts createPatchedFetcher2 CVEs · packages/next/src/server/lib/patch-fetch.ts handleAction2 CVEs · packages/next/src/server/app-render/action-handler.ts initialize2 CVEs · packages/next/src/server/lib/router-server.ts exportPageImpl2 CVEs · packages/next/src/export/worker.ts exportPagesPage2 CVEs · packages/next/src/export/routes/pages.ts

All patched functions in vercel/next.js

Frequently asked questions

Common questions about CVE fixes to setResponseHeaders.

How many CVEs have patched setResponseHeaders?: 2 published CVEs changed setResponseHeaders in vercel/next.js, in 2 distinct patches totalling 8 changed lines, between 2021 and 2022.
What is the latest CVE that changed setResponseHeaders?: CVE-2022-23646 (Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0), published 2022-02-17, changed lines 566 to 580 of packages/next/server/image-optimizer.ts.
How does setResponseHeaders compare to the rest of vercel/next.js?: vercel/next.js has 39 CVEs with a located fix in total; 2 of them changed setResponseHeaders.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track vercel/next.js CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing