Security readout for executives and security teams
Plain-English summary
A low-privileged Jenkins user could make Jenkins itself contact a chosen web address. That matters because Jenkins may reach internal systems ordinary users cannot. The sources confirm only forced GET requests, not data theft or code execution.
Executive priority
Treat this as a targeted Jenkins hardening item, especially where Jenkins can reach sensitive internal systems. It is not KEV-listed in the provided data, but old Jenkins plugins with broad access deserve prompt cleanup.
Technical view
CVE-2018-1000184 is a server-side request forgery issue in Jenkins GitHub Plugin 1.29.0 and older, in GitHubPluginConfig.java. Attackers with Overall/Read access can cause Jenkins to send a GET request to a specified URL.
Likely exposure
Exposure is likely limited to Jenkins instances running GitHub Plugin 1.29.0 or older where untrusted or broad user groups have Overall/Read access.
Exploitation context
The provided sources do not show CISA KEV listing, active exploitation, public exploit use, CVSS, CWE, or a confirmed impact beyond attacker-controlled GET requests.
Researcher notes
Evidence is sparse. The bundle identifies the vulnerable component, affected version range, file, access prerequisite, and SSRF GET behavior, but not CVSS, fixed version, exploit maturity, or detailed technical root cause.
Mitigation direction
- Inventory Jenkins controllers and installed GitHub Plugin versions.
- Review Jenkins SECURITY-799 for the vendor-supported upgrade or mitigation path.
- Upgrade affected GitHub Plugin installations according to Jenkins guidance.
- Restrict Overall/Read access to trusted Jenkins users only.
- Review network egress controls from Jenkins to internal services.
Validation and detection
- Confirm whether GitHub Plugin version is 1.29.0 or older.
- Review Jenkins authorization for users or groups with Overall/Read access.
- Check Jenkins logs for unusual outbound URL validation or GitHub configuration activity.
- Verify post-remediation plugin version is no longer in the affected range.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Cloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-1000184 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jenkins.io/security/advisory/2018-06-04/#SECURITY-799CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.