Skip to content
Fencer Vulns
high 8.8

CVE-2018-1000600 in the critical feed json

CSRF vulnerability and missing permission checks in GitHub Plugin allowed capturing credentials

published 2018-06-26 8 y ago modified 2026-06-17 4 mo ago also GHSA-6cvm-v6qj-hjq9 , EUVD-2022-2774

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
90.9%
EPSS 90.9% chance of exploitation in 30 days, percentile 99.8%
public exploits
0
none known, plus a Nuclei check

Summary

A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCredentialsCreator.java that allows attackers to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Patch / fix

  • maven com.coravy.hudson.plugins.github:github 1.29.2

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-2018-1000600 updated cvss 4.2

jenkins-plugin-github: CSRF vulnerability and missing permission checks in GitHub Plugin allowed capturing credentials (SECURITY-915)

  • Red Hat OpenShift Enterprise 3 jenkins-plugin-github
    affected: no fix available

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

90.89% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template Jenkins GitHub Plugin <=1.29.1 - Server-Side Request Forgery nuclei detection template

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven com.coravy.hudson.plugins.github:github
<1.29.2
1.29.2

Classification

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

References

Sources

Fencer Vulns 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.