LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41238: A missing permission check in Jenkins DotCi Plugin 2.40.00 and earlier allows unauthenticated attackers to...

A missing permission check in Jenkins DotCi Plugin 2.40.00 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository for attacker-specified commits.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This issue lets an unauthenticated person make Jenkins DotCi Plugin trigger builds for attacker-chosen repositories and commits. In business terms, exposed Jenkins systems could run untrusted build activity without normal permission checks, creating risk to source, build secrets, deployment workflows, and service availability.

Executive priority

Treat this as urgent for any Jenkins environment using DotCi Plugin. The main business risk is untrusted build activity reaching CI secrets, code, artifacts, or deployment paths. Prioritize internet-exposed Jenkins first.

Technical view

CVE-2022-41238 is a CWE-862 missing authorization check in Jenkins DotCi Plugin 2.40.00 and earlier. The provided CVE record says unauthenticated attackers can trigger builds for jobs tied to attacker-specified repositories and commits. CVSS 3.1 is 9.8 critical, with network attack vector and no privileges or user interaction required.

Likely exposure

Organizations are exposed if they run Jenkins with DotCi Plugin 2.40.00 or earlier, especially where Jenkins or relevant webhook endpoints are reachable by untrusted networks. The source bundle does not identify other affected products.

Exploitation context

The provided sources do not state active exploitation, and the bundle marks KEV as false. The vulnerability is still high urgency because unauthenticated network attackers can trigger build execution paths without permission checks.

Researcher notes

Evidence is limited to the CVE metadata and Jenkins advisory reference in the bundle. Do not assume a specific patch version or exploit in the wild from these sources. Focus validation on plugin presence, version, exposure, and suspicious build-trigger activity.

Mitigation direction

  • Inventory Jenkins controllers for DotCi Plugin usage and version.
  • Review the Jenkins advisory and plugin guidance for supported remediation.
  • Disable or remove DotCi Plugin where it is not required.
  • Restrict Jenkins access to trusted networks while remediation is assessed.
  • Review build jobs for secrets or deployment permissions reachable through DotCi.

Validation and detection

  • Confirm whether DotCi Plugin is installed on each Jenkins controller.
  • Verify installed versions are not 2.40.00 or earlier.
  • Check whether Jenkins is reachable from untrusted networks.
  • Review logs for unexpected DotCi-triggered builds or unusual repository inputs.
  • Confirm compensating access controls do not rely on the missing plugin permission check.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41238 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-41238Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jenkins projectJenkins DotCi Pluginunspecified, next of 2.40.00Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.