{"answers":{"affected":"2 open source packages ship an affected version, including org.eclipse.jetty:jetty-server. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17638 in the wild and no public exploit code.","fix":"Upgrade org.eclipse.jetty:jetty-server to 9.4.30.v20200611 or later.","what":"CVE-2019-17638 is a critical vulnerability in Eclipse Jetty, published on 9 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-17638 and fix it if it is affected.\n\nWhat it is: CVE-2019-17638 is a critical vulnerability in Eclipse Jetty, published on 9 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-17638 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.eclipse.jetty:jetty-server (Maven): affected from 9.4.27; fixed in 9.4.30.v20200611\n- org.eclipse.jetty:jetty-server (Maven): affected from 9.4.27; fixed in 9.4.30.v20200611\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-17638/ (Markdown: https://insights.sbomify.com/CVE-2019-17638/index.md)","id":"CVE-2019-17638","markdown":"https://insights.sbomify.com/CVE-2019-17638/index.md","name":"CVE-2019-17638","record":{"aliases":["DEBIAN-CVE-2019-17638","GHSA-x3rh-m7vp-35f2"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jetty web server","requires_auth":"none","summary":"A race condition in Eclipse Jetty allows attackers to view sensitive data from other users' requests due to double-release of response buffers.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"jetty","vendor":"eclipse"}],"cvss":{"score":9.4,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-675","name":"Multiple Operations on Resource in Single-Operation Context"},{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"}],"description":"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).","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2021-02-04","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-02-04T05:07:42Z","kind":"github_poc","ref":"https://github.com/forse01/CVE-2019-17638-Jetty","stars":1,"title":null}],"tier":"poc_unverified"},"has_fix":true,"headline":"Operation on a Resource after Expiration or Release in Jetty Server","id":"CVE-2019-17638","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"eclipse:jetty","products":["eclipse:jetty"],"type":"race_condition","year":"2019"},"n_packages":2,"n_references":17,"next":{"headline":"Memory corruption in Eclipse OpenJ9","id":"CVE-2019-17639"},"packages":[{"ecosystem":"Maven","fixed":["9.4.30.v20200611"],"introduced":["9.4.27"],"last_affected":[],"package":"org.eclipse.jetty:jetty-server","purl":null,"source":"GHSA-x3rh-m7vp-35f2"},{"ecosystem":"Maven","fixed":["9.4.30.v20200611"],"introduced":["9.4.27"],"last_affected":[],"package":"org.eclipse.jetty:jetty-server","purl":"pkg:maven/org.eclipse.jetty/jetty-server","source":"GHSA-x3rh-m7vp-35f2"}],"prev":{"headline":"XML external entity in Eclipse Web Tools Platform","id":"CVE-2019-17637"},"products":["Eclipse Jetty"],"published":"2020-07-09","related":[{"cvss_score":9.8,"headline":"Jetty contains an alias issue that could allow unauthenticated remote code execution due to specially crafted request","id":"CVE-2016-4800","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":8.8,"headline":"Access and integrity issue within Eclipse Jetty","id":"CVE-2018-12538","kev_date_added":null,"published":"2018-06-22"},{"cvss_score":8.7,"headline":"Digest authentication lossy encoding","id":"CVE-2026-10050","kev_date_added":null,"published":"2026-08-04"},{"cvss_score":7.7,"headline":"MadeYouReset HTTP/2 vulnerability","id":"CVE-2025-5115","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":7.5,"headline":"Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests","id":"CVE-2024-7708","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7.5,"headline":"The Eclipse Jetty Server Artifact has a Gzip request memory leak","id":"CVE-2026-1605","kev_date_added":null,"published":"2026-03-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["The Eclipse Foundation"]},"summary":"A race condition in Eclipse Jetty allows attackers to view sensitive data from other users' requests due to double-release of response buffers.","url":"https://insights.sbomify.com/CVE-2019-17638/"}