CVE-2023-44487: The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

High CVSS 7.5

CVE id
CVE-2023-44487
Published
Last modified

Affected packages

PackageAffected versionsFixed in
Caddy
Runtimes and servers
< 2.7.5 2.7.5
.NET
Runtimes and servers
>= 6.0.0, < 6.0.23
>= 7.0.0, < 7.0.12
6.0.23, 7.0.12
Envoy
Runtimes and servers
1.24.10
1.25.9
1.26.4
1.27.0
not fixed yet
Go
Runtimes and servers
< 1.20.10
>= 1.21.0, < 1.21.3
1.20.10, 1.21.3
Jenkins
Runtimes and servers
<= 2.427 after 2.427
Jenkins LTS
Runtimes and servers
<= 2.414.2 after 2.414.2
NGINX
Runtimes and servers
>= 1.9.5, <= 1.25.2 after 1.25.2
F5 NGINX Ingress Controller
Runtimes and servers
>= 2.0.0, <= 2.4.2
>= 3.0.0, <= 3.3.0
after 2.4.2, 3.3.0
NGINX Plus
Runtimes and servers
>= 25, < 29
>= 29, < 30
>= 30, < 31
29, 30, 31
Node.js
Runtimes and servers
>= 18.0.0, < 18.18.2
>= 20.0.0, < 20.8.1
18.18.2, 20.8.1
Apache Solr
Runtimes and servers
< 9.4.0 9.4.0
Apache Tomcat
Runtimes and servers
>= 8.5.0, <= 8.5.93
>= 9.0.0, <= 9.0.80
>= 10.1.0, <= 10.1.13
after 8.5.93, 9.0.80, 10.1.13
Traefik
Runtimes and servers
< 2.10.5 2.10.5
Varnish Cache
Runtimes and servers
see the advisory not fixed yet

How to fix it

Caddy (Runtimes and servers)

Upgrade Caddy to 2.7.5 or later.

caddy version
  • Upgrade Caddy (the caddy image tag or binary) to the patched release.

.NET (Runtimes and servers)

Upgrade .NET to the fixed release of the line you run: 6.0.23, 7.0.12.

dotnet --list-runtimes
  • Install the patched .NET runtime of your major line (and the matching SDK), update the aspnet/runtime image tag, and redeploy.

Envoy (Runtimes and servers)

No fix yet. No fixed Envoy release is listed yet.

envoy --version
  • Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
  • Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
  • Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.

Go (Runtimes and servers)

Upgrade Go to the fixed release of the line you run: 1.20.10, 1.21.3.

go version
  • Build with the patched Go release (set "toolchain" in go.mod, or the golang image tag) and redeploy: Go programs include the standard library, so they must be rebuilt.

Jenkins (Runtimes and servers)

Upgrade Jenkins to a release newer than 2.427.

curl -sI $JENKINS_URL | grep X-Jenkins
  • Upgrade Jenkins to the patched weekly release (the jenkins/jenkins image tag or your packages) and restart it.

Jenkins LTS (Runtimes and servers)

Upgrade Jenkins LTS to a release newer than 2.414.2.

curl -sI $JENKINS_URL | grep X-Jenkins
  • Upgrade Jenkins to the patched LTS release (the jenkins/jenkins:lts image tag or your packages) and restart it.

NGINX (Runtimes and servers)

Upgrade NGINX to a release newer than 1.25.2.

nginx -v
  • Install the patched NGINX release of your branch (the nginx image tag, the nginx.org packages, or your distribution's security update) and restart NGINX; with OpenResty, upgrade to the OpenResty release built on it.

F5 NGINX Ingress Controller (Runtimes and servers)

Upgrade F5 NGINX Ingress Controller to a release newer than the last affected update of the line you run (2.4.2, 3.3.0).

kubectl get deploy -A -l app.kubernetes.io/name=nginx-ingress -o jsonpath='{..image}'
  • Upgrade the NGINX Ingress Controller image (nginx/nginx-ingress or nginx-plus-ingress) or its Helm chart to the patched release and roll it out to every cluster.

NGINX Plus (Runtimes and servers)

Upgrade NGINX Plus to the fixed release of the line you run: 29, 30, 31.

nginx -v
  • Upgrade NGINX Plus to the patched release from the F5 repository (or your nginx-plus image) and restart it.

Node.js (Runtimes and servers)

Upgrade Node.js to the fixed release of the line you run: 18.18.2, 20.8.1.

node --version
  • Install the patched Node.js release of your major line (nvm install, or the node image tag) everywhere the app runs and builds.

Apache Solr (Runtimes and servers)

Upgrade Apache Solr to 9.4.0 or later.

  • Upgrade Solr (the solr image tag) to the patched release.

Apache Tomcat (Runtimes and servers)

Upgrade Apache Tomcat to a release newer than the last affected update of the line you run (8.5.93, 9.0.80, 10.1.13).

catalina.sh version
  • Install the patched Tomcat release of your branch (the tomcat image tag, or your tomcat packages) and restart it.

Traefik (Runtimes and servers)

Upgrade Traefik to 2.10.5 or later.

traefik version
  • Upgrade Traefik (the traefik image tag or its Helm chart) to the patched release.

Varnish Cache (Runtimes and servers)

No fix yet. No fixed Varnish Cache release is listed yet.

varnishd -V
  • Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
  • Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
  • Install the patched Varnish Cache release (the varnish image tag or your packages) and restart varnishd.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.