CVE-2017-9735

CVE-2017-9735 is a high-severity vulnerability in Eclipse Jetty with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-203.

Key facts

Description

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.

Frequently asked questions

What is CVE-2017-9735?
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.
How severe is CVE-2017-9735?
CVE-2017-9735 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2017-9735 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 6% (92nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-9735?
CVE-2017-9735 primarily affects Eclipse Jetty. In total, 15 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-9735?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-9735 published?
CVE-2017-9735 was published on 2017-06-16 and last updated on 2026-06-17.

References

Affected products (15)

More vulnerabilities in Eclipse Jetty

All CVEs affecting Eclipse Jetty →

Other CWE-203 (Observable Discrepancy) vulnerabilities

Browse all CWE-203 (Observable Discrepancy) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: