Skip to content
Fencer Intel
critical 9.4

CVE-2019-17638 in the critical feed json

Operation on a Resource after Expiration or Release in Jetty Server

published 6y ago modified 4mo ago also GHSA-x3rh-m7vp-35f2 , EUVD-2020-0652

cvss
9.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
11.1%
EPSS 11.1% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

In Eclipse Jetty, versions 9.4.27.v20200227 to 9.4.29.v20200521, in case of too large response headers, Jetty throws an exception to produce an HTTP 431 error. When this happens, the ByteBuffer containing the HTTP response headers is released back to the ByteBufferPool twice. Because of this double release, two threads can acquire the same ByteBuffer from the pool and while thread1 is about to use the ByteBuffer to write response1 data, thread2 fills the ByteBuffer with other data. Thread1 then proceeds to write the buffer that now contains different data. This results in client1, which issued request1 seeing data from another request or response which could contain sensitive data belonging to client2 (HTTP session ids, authentication credentials, etc.). If the Jetty version cannot be upgraded, the vulnerability can be significantly reduced by configuring a responseHeaderSize significantly larger than the requestHeaderSize (12KB responseHeaderSize and 8KB requestHeaderSize).

Patch / fix

  • maven org.eclipse.jetty:jetty-server 9.4.30.v20200611
  • jetty9 Debian 14, Debian 13, Debian 12 9.4.31-1

debian advisories DEBIAN-CVE-2019-17638

  • jenkins openshift 3.11 2.235.5.1600415953-1.el7
  • jenkins openshift 4.5 2.235.5.1600414805-1.el7
  • jenkins openshift 4.3 2.235.5.1600415514-1.el7
  • openshift openshift 4.3 4.3.37-202009120213.p0.git.0.dffefe4.el8
  • openshift-hyperkube openshift 4.3 4.3.37-202009120213.p0.git.0.dffefe4.el8

red hat advisories RHSA-2020:4223RHSA-2020:3841RHSA-2020:3808

Is CVE-2019-17638 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-17638 updated cvss 7.7

jetty: double release of resource can lead to information disclosure

  • Red Hat Fuse 7.8.0
    fixed: vendor fix RHSA-2020:5568
  • Red Hat OpenShift Container Platform 3.11 jenkins 2.235.5.1600415953-1.el7
    fixed: vendor fix RHSA-2020:4223
  • Red Hat OpenShift Container Platform 4.3 jenkins 2.235.5.1600415514-1.el7
    fixed: vendor fix RHSA-2020:3808
  • Red Hat OpenShift Container Platform 4.4 openshift4/ose-jenkins v4.4.0-202009260441.p0
    fixed: vendor fix RHSA-2020:4220
  • Red Hat OpenShift Container Platform 4.5 jenkins 2.235.5.1600414805-1.el7
    fixed: vendor fix RHSA-2020:3841
  • Red Hat OpenShift Container Platform 4.6 openshift4/ose-cli v4.6.0-202010311441.p0, openshift4/ose-pod v4.6.0-202010311441.p0, openshift4/ose-etcd v4.6.0-202010311441.p0, openshift4/ose-tests v4.6.0-202010311441.p0, openshift4/ose-console v4.6.0-202011020726.p0, openshift4/ose-coredns v4.6.0-202010311441.p0, +119 more
    fixed: vendor fix RHBA-2020:4339
  • Red Hat Enterprise Linux 6 jetty-eclipse Red Hat Enterprise Linux 7 jetty-io, jetty-ant, jetty-jmx, jetty-jsp, jetty-xml, jetty-http, +30 more Red Hat JBoss Fuse 6 jetty Red Hat JBoss Fuse Service Works 6 jetty Red Hat OpenShift Container Platform 4.3 openshift 4.3.37-202009120213.p0.git.0.dffefe4.el8, openshift-hyperkube 4.3.37-202009120213.p0.git.0.dffefe4.el8 Red Hat Single Sign-On 7 jetty
    +1 more products
    Red Hat Software Collections rh-java-common-jetty-io, rh-java-common-jetty-ant, rh-java-common-jetty-jmx, rh-java-common-jetty-jsp, rh-java-common-jetty-xml, rh-java-common-jetty-http, +30 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

11.14% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.4 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

Affected packages

ecosystem package affected fixed in
maven org.eclipse.jetty:jetty-server
>=9.4.27, <9.4.30.v20200611
9.4.30.v20200611

Affected products

  • The Eclipse Foundation Eclipse Jetty

Classification

Weakness
  • CWE-672 Operation on a Resource after Expiration or Release
  • CWE-675 Multiple Operations on Resource in Single-Operation Context

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.