Skip to content
Fencer Intel
high 7.5

CVE-2017-9735 json

Jetty vulnerable to exposure of sensitive information due to observable discrepancy

published 2017-06-16 9 y ago modified 2026-06-17 4 mo ago also GHSA-wfcc-pff6-rgc5 , EUVD-2018-0708

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.6%
EPSS 9.6% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Jetty through 9.4.x is prone to a timing channel in util/security/Password.java, which makes it easier for remote attackers to obtain access by observing elapsed times before rejection of incorrect passwords.

Patch / fix

  • maven org.eclipse.jetty:jetty-server 9.2.22.v20170606, 9.3.20.v20170531, 9.4.6.v20170531
  • eclipse jetty 9.2.22, 9.3.20, 9.4.6
  • jetty9 Debian 14, Debian 13, Debian 12 9.2.22-1

debian advisories DEBIAN-CVE-2017-9735

  • jetty Ubuntu 14.04 LTS 6.1.26-1ubuntu1.2
  • jetty Ubuntu 16.04 LTS 6.1.26-5ubuntu0.1

ubuntu advisories UBUNTU-CVE-2017-9735

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-9735 updated cvss 5.1

jetty: Timing channel attack in util/security/Password.java

  • Red Hat Enterprise Linux 6 jetty-eclipse Red Hat Enterprise Linux 7 jetty-io, jetty-ant, jetty-jmx, jetty-jsp, jetty-xml, jetty-http, +30 more
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse Integration Service 2 jetty
    affected: no fix available
  • Red Hat Software Collections rh-java-common-jetty-io, rh-java-common-jetty-ant, rh-java-common-jetty-jmx, rh-java-common-jetty-jsp, rh-java-common-jetty-xml, rh-java-common-jetty-http, +30 more
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.64% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.eclipse.jetty:jetty-server
>=9.4.0, <9.4.6.v20170531
>=9.3.0, <9.3.20.v20170531
<9.2.22.v20170606
9.4.6.v20170531
9.3.20.v20170531
9.2.22.v20170606

Classification

Weakness
  • CWE-203 Observable Discrepancy
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.