LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41237: Jenkins DotCi Plugin 2.40.00 and earlier does not configure its YAML parser to prevent the instantiation of...

Jenkins DotCi Plugin 2.40.00 and earlier does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerability.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Jenkins DotCi Plugin 2.40.00 and earlier can process YAML in a way that may create arbitrary Java object types, leading to remote code execution. For affected Jenkins environments, this is business-critical because compromise could expose build secrets, source code, deployment credentials, and CI/CD integrity.

Executive priority

Treat as urgent for any Jenkins environment using DotCi Plugin. CI/CD compromise can become a route to source code, secrets, and production deployment systems. If the plugin is absent, priority drops substantially.

Technical view

The issue is unsafe deserialization/class instantiation in YAML parsing, mapped to CWE-502. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Jenkins deployments running the DotCi Plugin version 2.40.00 or earlier. The source bundle does not confirm default installation, internet exposure, or affected configuration paths.

Exploitation context

The CVSS vector indicates remote unauthenticated exploitability without user interaction. The provided data does not show CISA KEV listing or cited evidence of active exploitation, so active exploitation should not be asserted.

Researcher notes

Evidence supports a YAML parser configuration flaw enabling arbitrary type instantiation and RCE. The bundle does not include a fixed version, exploit proof, affected endpoints, or vendor mitigation details beyond the Jenkins advisory reference.

Mitigation direction

  • Inventory Jenkins controllers for the DotCi Plugin and its version.
  • Check Jenkins advisory and plugin guidance for fixed-version or removal instructions.
  • Prioritize affected Jenkins systems that are internet-facing or handle deployment secrets.
  • Restrict Jenkins access while remediation guidance is being confirmed.
  • Review CI/CD credentials and secrets if compromise is suspected.

Validation and detection

  • Confirm whether DotCi Plugin is installed on each Jenkins controller.
  • Verify installed plugin versions are not 2.40.00 or earlier.
  • Review Jenkins logs for unexpected DotCi job activity or plugin errors.
  • Confirm Jenkins exposure boundaries, including VPN, SSO, and public access.
  • Document compensating controls if vendor remediation is unavailable.
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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-41237 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-41237Attack 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-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.