Security readout for executives and security teams
Plain-English summary
Jenkins AWS Global Configuration Plugin 1.5 and earlier had an authorization flaw. A user with only Jenkins Overall/Read permission could replace the global AWS configuration, which may disrupt automation or redirect jobs toward attacker-controlled AWS settings.
Executive priority
Prioritize remediation where Jenkins controls production deployment, cloud automation, or AWS credentials. The flaw can let low-privileged Jenkins users alter global AWS settings, creating operational and security risk.
Technical view
The issue is a missing permission check in Jenkins AWS Global Configuration Plugin. The CVE states attackers with Overall/Read can replace the global AWS configuration. No CVSS, CWE, exploit details, or confirmed active exploitation are provided in the source bundle.
Likely exposure
Exposure is limited to Jenkins instances using AWS Global Configuration Plugin 1.5 or earlier, especially where Overall/Read is granted broadly to non-administrators.
Exploitation context
The sources do not report active exploitation, and CISA KEV status is false. Exploitation requires authenticated Jenkins access with Overall/Read permission, not anonymous access based on the provided description.
Researcher notes
The CVE record is sparse: no CVSS, CWE, exploit status, or detailed fix text is included in the bundle. Version data should be validated against the Jenkins advisory because the affected metadata is incomplete while the title names 1.5 and earlier.
Mitigation direction
- Identify Jenkins instances with AWS Global Configuration Plugin installed.
- Check plugin version and compare against Jenkins advisory guidance.
- Upgrade or remove the plugin according to Jenkins guidance.
- Limit Overall/Read permission to trusted users until remediated.
- Review global AWS configuration for unauthorized changes.
Validation and detection
- Inventory Jenkins controllers and installed plugin versions.
- Confirm whether AWS Global Configuration Plugin is version 1.5 or earlier.
- Review Jenkins authorization strategy for broad Overall/Read grants.
- Audit recent changes to global AWS configuration.
- Check vendor advisory for fixed-version details.
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-2020-2311 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://www.jenkins.io/security/advisory/2020-11-04/#SECURITY-2101CVE 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.