In Eclipse Jetty, the Digest authentication server-side component uses ISO-8859-1 to encode the password as bytes. This was done because the initial specification for HTTP did not specify explicitly a charset, and it was assumed to be ISO-8859-1 for historical reasons. If the password contains characters that cannot be represented in ISO-8859-1, they are silently replaced by `?`. This happens with passwords that contain Chinese, Cyrillic or Greek characters, for example: `αβ123` converts to `??123`. An attacker can send a request with a digest `Authorization` header crafted with a password made of only `?` characters; the server would match any password of the same length that contains non-ISO-8859-1 characters. Recent HTTP Digest [RFC-7616](https://datatracker.ietf.org/doc/html/rfc7616) supports a `charset` parameters that defaults to UTF-8 that allows for correct encoding/decoding of passwords.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XEclipse Jetty
APPEclipse9.4.0 – 9.4.63 (excl.)10.0.0 – 10.0.31 (excl.)11.0.0 – 11.0.31 (excl.)12.0.0 – 12.0.36 (excl.)12.1.0 – 12.1.10 (excl.)
Related vulnerabilities
Eclipse Jetty: wyciek danych między sesjami przez double-release ByteBuffer
Eclipse Jetty: integer overflow w parsowaniu chunk length — obejście autoryzacji
Eclipse Jetty — pominięcie autoryzacji przez HTTP Request Smuggling
Eclipse Jetty: ominięcie zabezpieczeń przez nieprawidłową normalizację ścieżek URL (Windows)
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can ...