<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 09:05:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-10050 — Digest authentication lossy encoding</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-10050</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Eclipse Jetty - EE8, Eclipse Foundation Eclipse Jetty - EE9, Eclipse Foundation Eclipse Jetty&lt;/p&gt;
&lt;p&gt;In Eclipse Jetty, the Digest authentication server-side component uses ISO-8859-1 to encode the password as bytes.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Eclipse Jetty - EE8, Eclipse Foundation Eclipse Jetty - EE9, Eclipse Foundation Eclipse Jetty&lt;/p&gt;
&lt;p&gt;In Eclipse Jetty, the Digest authentication server-side component uses ISO-8859-1 to encode the password as bytes.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-10050</guid>
    </item>
  </channel>
</rss>
