Security readout for executives and security teams
Plain-English summary
Jenkins Git Plugin 3.7.0 and earlier could let a network-accessible attacker view Jenkins node and user lists without proper authorization. This is information disclosure, not direct code execution in the provided sources, but exposed identity and infrastructure details can support later attacks.
Executive priority
Prioritize remediation for internet-facing or broadly reachable Jenkins systems. Business urgency is moderate because the issue exposes user and node information that can aid follow-on attacks, but the provided sources do not show code execution or active exploitation.
Technical view
The CVE describes an improper authorization issue in GitStatus.java in Jenkins Git Plugin through version 3.7.0. An attacker with network access may obtain lists of Jenkins nodes and users. The bundle provides no CVSS score, CWE mapping, proof of active exploitation, or explicit fixed version.
Likely exposure
Organizations running Jenkins with Git Plugin 3.7.0 or earlier are the likely exposure group, especially where Jenkins is reachable beyond tightly controlled administrative networks. The provided data does not identify other affected products or configurations.
Exploitation context
The source bundle does not show CISA KEV status or any cited evidence of active exploitation. Exploitation requires network access to the affected Jenkins instance. The known impact is unauthorized enumeration of nodes and users.
Researcher notes
Evidence is limited to the CVE description and Jenkins advisory reference. Do not assume exploit availability, broader product impact, or a specific fixed version from this bundle alone. Focus validation on Git Plugin version, Jenkins reachability, and unauthorized visibility of users and nodes.
Mitigation direction
- Inventory Jenkins Git Plugin versions across all Jenkins instances.
- Treat Git Plugin 3.7.0 and earlier as affected.
- Review Jenkins SECURITY-723 for vendor-approved upgrade or mitigation guidance.
- Restrict Jenkins network access to trusted administrative users and networks.
- Review Jenkins logs for unusual status or enumeration activity.
Validation and detection
- Confirm installed Jenkins Git Plugin version on each Jenkins instance.
- Verify Jenkins instances are not exposed to untrusted networks.
- Check whether remediation guidance from Jenkins SECURITY-723 has been applied.
- Confirm non-administrative users cannot enumerate Jenkins nodes or users.
- Document remaining affected instances and ownership for remediation tracking.
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.
CVE-2018-1000110 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-02-26/#SECURITY-723CVE 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.