CVE-2017-26114.3MediumCWE-358

CVE-2017-2611: jenkins vulnerability

Jenkins · jenkins

Affected: jenkins · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.9%probability of exploitation in the next 30 days

80th percentile

050100

Higher than 80% of scored CVEs

4.3MediumCVSS 3.0

LowMediumHighCrit.

DescriptionCVE.org

Jenkins before versions 2.44, 2.32.2 is vulnerable to an insufficient permission check for periodic processes (SECURITY-389). The URLs /workspaceCleanup and /fingerprintCleanup did not perform permission checks, allowing users with read access to Jenkins to trigger these background processes (that are otherwise performed daily), possibly causing additional load on Jenkins master and agents.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

jenkinsjenkins 2.44; jenkins 2.32.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improperly Implemented Security Check for Standard · Cryptography
Vendor: Jenkins
Published: May 2018
Band: Possible (1 to 10%), May 2018

CoverageNo articles yet

No CyberSIXT article names CVE-2017-2611 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.