HighGHSA-26vr-8j45-3r4wBIT-jenkins-2021-28165CVE-2021-28165

Jetty vulnerable to incorrect handling of invalid large TLS frame, exhausting CPU resources

Published 6 Apr 2021 · Updated 8 Jul 2026

Is your project on an affected org.eclipse.jetty:jetty-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=7.2.2 <9.4.39
Fixed in
9.4.39
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=9.4.39 -DforceVersion=true
Affected
>=10.0.0 <10.0.2
Fixed in
10.0.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=10.0.2 -DforceVersion=true
Affected
>=11.0.0 <11.0.2
Fixed in
11.0.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.eclipse.jetty:jetty-server -DdepVersion=11.0.2 -DforceVersion=true

Details

Impact

When using SSL/TLS with Jetty, either with HTTP/1.1, HTTP/2, or WebSocket, the server may receive an invalid large (greater than 17408) TLS frame that is incorrectly handled, causing CPU resources to eventually reach 100% usage.

Workarounds

The problem can be worked around by compiling the following class:

package org.eclipse.jetty.server.ssl.fix6072;

import java.nio.ByteBuffer;
import javax.net.ssl.SSLEngine;
import javax.net.ssl.SSLEngineResult;
import javax.net.ssl.SSLException;
import javax.net.ssl.SSLHandshakeException;

import org.eclipse.jetty.io.EndPoint;
import org.eclipse.jetty.io.ssl.SslConnection;
import org.eclipse.jetty.server.Connector;
import org.eclipse.jetty.server.SslConnectionFactory;
import org.eclipse.jetty.util.BufferUtil;
import org.eclipse.jetty.util.annotation.Name;
import org.eclipse.jetty.util.ssl.SslContextFactory;

public class SpaceCheckingSslConnectionFactory extends SslConnectionFactory
{
    public SpaceCheckingSslConnectionFactory(@Name("sslContextFactory") SslContextFactory factory, @Name("next") String nextProtocol)
    {
        super(factory, nextProtocol);
    }

    @Override
    protected SslConnection newSslConnection(Connector connector, EndPoint endPoint, SSLEngine engine)
    {
        return new SslConnection(connector.getByteBufferPool(), connector.getExecutor(), endPoint, engine, isDirectBuffersForEncryption(), isDirectBuffersForDecryption())
        {
            @Override
            protected SSLEngineResult unwrap(SSLEngine sslEngine, ByteBuffer input, ByteBuffer output) throws SSLException
            {
                SSLEngineResult results = super.unwrap(sslEngine, input, output);

                if ((results.getStatus() == SSLEngineResult.Status.BUFFER_UNDERFLOW ||
                    results.getStatus() == SSLEngineResult.Status.OK && results.bytesConsumed() == 0 && results.bytesProduced() == 0) &&
                    BufferUtil.space(input) == 0)
                {
                    BufferUtil.clear(input);
                    throw new SSLHandshakeException("Encrypted buffer max length exceeded");
                }
                return results;
            }
        };
    }
}

This class can be deployed by: + The resulting class file should be put into a jar file (eg sslfix6072.jar) + The jar file should be made available to the server. For a normal distribution this can be done by putting the file into ${jetty.base}/lib + Copy the file ${jetty.home}/modules/ssl.mod to ${jetty.base}/modules + Edit the ${jetty.base}/modules/ssl.mod file to have the following section:

[lib]
lib/sslfix6072.jar

+ Copy the file ${jetty.home}/etc/jetty-https.xml and${jetty.home}/etc/jetty-http2.xml to ${jetty.base}/etc + Edit files ${jetty.base}/etc/jetty-https.xml and ${jetty.base}/etc/jetty-http2.xml, changing any reference of org.eclipse.jetty.server.SslConnectionFactory to org.eclipse.jetty.server.ssl.fix6072.SpaceCheckingSslConnectionFactory. For example:

  <Call name="addIfAbsentConnectionFactory">
    <Arg>
      <New class="org.eclipse.jetty.server.ssl.fix6072.SpaceCheckingSslConnectionFactory">
        <Arg name="next">http/1.1</Arg>
        <Arg name="sslContextFactory"><Ref refid="sslContextFactory"/></Arg>
      </New>
    </Arg>
  </Call>

+ Restart Jetty

Is GHSA-26vr-8j45-3r4w in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.eclipse.jetty:jetty-server, and gives you the command that fixes it.

More advisories for org.eclipse.jetty:jetty-server

  • HighCVE-2024-7708Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests · 22 Jul 2026
  • MediumCVE-2026-6790Eclipse Jetty: HTTP Authority/Host mismatch · 22 Jul 2026
  • MediumCVE-2026-10051Eclipse Jetty: Cross-Request Leakage for trailers on HTTP/1.1 keep-alive connections · 22 Jul 2026
  • HighCVE-2026-1605The Eclipse Jetty Server Artifact has a Gzip request memory leak · 5 Mar 2026
  • HighCVE-2024-13009**UNSUPPORTED WHEN ASSIGNED** GzipHandler causes part of request body to be seen as request body of a separate request · 8 May 2025
  • MediumCVE-2024-8184Eclipse Jetty's ThreadLimitHandler.getRemote() vulnerable to remote DoS attacks · 14 Oct 2024
All 29 advisories for org.eclipse.jetty:jetty-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.