CVE-2017-2609

Name: CVE-2017-2609
Creator: NVD / NIST
Published: 2018-05-22T17:29:00.33+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.82%

Last modified Jun 17, 2026

CVE-2017-2609 is a vulnerability of currently unknown severity. jenkins before versions 2.44, 2.32.2 is vulnerable to an information disclosure vulnerability in search suggestions (SECURITY-385). The autocomplete feature on the search box discloses the names of the views in its suggestions, including the ones for which the current user does not have access to.. EPSS estimates a 1.82% chance of exploitation in the next 30 days.

Description

jenkins before versions 2.44, 2.32.2 is vulnerable to an information disclosure vulnerability in search suggestions (SECURITY-385). The autocomplete feature on the search box discloses the names of the views in its suggestions, including the ones for which the current user does not have access to.

Metrics

EPSS Probability

1.82%

76.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Jenkins	Jenkins	< 2.32.2
Jenkins	Jenkins	< 2.44

References

http://www.securityfocus.com/bid/95964Third Party Advisory, VDB Entry
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2609Issue Tracking, Patch, Third Party Advisory
https://github.com/jenkinsci/jenkins/commit/13905d8224899ba7332fe9af4e330ea96a2ae319Patch, Third Party Advisory
http://www.securityfocus.com/bid/95964Third Party Advisory, VDB Entry
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2609Issue Tracking, Patch, Third Party Advisory
https://github.com/jenkinsci/jenkins/commit/13905d8224899ba7332fe9af4e330ea96a2ae319Patch, Third Party Advisory

Timeline

Published: May 22, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2017-2609?

How severe is CVE-2017-2609?

Severity scoring for CVE-2017-2609 is pending analysis. The EPSS model estimates a 1.82% probability of exploitation in the next 30 days.

How do I fix CVE-2017-2609?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2017-2609?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST