CVEvulnerability

CVE-2026-10050

8.7 HIGH Published 2026-08-04 Modified 2026-08-08 Official page ↗
Status
Analyzed
Published
2026-08-04
Last modified
2026-08-08
Assigner
[email protected]
CVSS 4.0 ([email protected])
8.7 HIGH — 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:X
CVSS 3.1 ([email protected])
9.1 CRITICAL — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Weaknesses
CWE-173, CWE-303

Description

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 supports a `charset` parameters that defaults to UTF-8 that allows for correct encoding/decoding of passwords.

Affected configurations

• eclipse jetty (>= 9.4.0 < 9.4.63) • eclipse jetty (>= 10.0.0 < 10.0.31) • eclipse jetty (>= 11.0.0 < 11.0.31) • eclipse jetty (>= 12.0.0 < 12.0.36) • eclipse jetty (>= 12.1.0 < 12.1.10)

Related

Weakness · CWE (2)

  • CWE-173 Improper Handling of Alternate Encoding weakness
  • CWE-303 Incorrect Implementation of Authentication Algorithm weakness

References