[Eclipse Jetty] JASPI access control escalation

The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.

Basic information

Project name: Eclipse Jetty

Project id: rt/jetty

Request type: reservation

Versions affected:

>=12.1.0,<=12.1.7
>=12.0.0,<=12.0.33
>=11.0.0, <=11.0.28
>=10.0.0, <=10.0.28
>=9.4.0, <=9.4.60

Common Weakness Enumeration (CWE):

• CWE-226
• CWE-287

Common Attack Pattern Enumerations and Classifications (CAPEC):

• None

Common Vulnerability Scoring System: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Summary:

In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable.

Upon returning from the initial checks, there are conditions that cause an early return from the JASPIAuthenticator code without clearing those ThreadLocals.

A subsequent request using the same thread inherits the ThreadLocal values, leading to a broken access control and privilege escalation.

Links:

• https://github.com/jetty/jetty.project/security/advisories/GHSA-r7p8-xq5m-436c

Credits:

• https://github.com/HRsGIT

Tracking

This section will completed by the project team.

• Reserve an entry only
• We're ready for this issue to be reported to the central authority (i.e., make this public now)
• (when applicable) The GitHub Security Advisory is ready to be published now

Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.

This section will be completed by the EMO.

CVE: {cve}

• All required information is provided
• CVE Assigned
• Pushed to Mitre
• Accepted by Mitre