dbcve.org
DatadogApplication · Jenkins

CVE-2023-37944

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to 5.4.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A missing permission check in Jenkins Datadog Plugin 5.4.1 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Jenkins Datadog Plugin before 5.4.2 fails to perform permission checks on a method that allows connecting to user-specified URLs using attacker-controlled credential IDs. An attacker with only Overall/Read permission (the lowest privilege in Jenkins) can exploit this to make the Jenkins instance connect to attacker-controlled servers and capture stored credentials.

MitigationUpgrade Jenkins Datadog Plugin to version 5.4.2 or later which includes the missing permission check. If unable to upgrade immediately, restrict Overall/Read permission to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DatadogApplication
Affected:< 5.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Datadog plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: jenkins-cli.jar who-am-i or check the plugin directory $JENKINS_HOME/plugins for datadog plugin files
    Affected if The Datadog plugin appears in the installed plugins list
  2. Check installed Datadog plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed > Datadog Plugin, note the version number. Compare against the fixed version 5.4.2
    Affected if The installed version is lower than 5.4.2 (e.g., 5.4.1, 5.4.0, etc.)
  3. Identify users with Overall/Read permission
    Navigate to Manage Jenkins > Manage Users or check $JENKINS_HOME/users/ directory and review authorization matrix settings at Configure Global Security
    Affected if Untrusted or anonymous users have been granted Overall/Read permission (this is the minimum privilege required to exploit)
  4. Review configured credentials
    Navigate to Manage Jenkins > Manage Credentials to inspect stored credentials, particularly any that could be used by the vulnerable method
    Affected if Any credentials are stored in Jenkins that could be leveraged by the plugin's vulnerable method

A user is affected if the Datadog plugin version is below 5.4.2 AND untrusted users have Overall/Read permission AND credentials exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.4.2 or later
Fixed in 5.4.2
Interim mitigation

Upgrade Jenkins Datadog Plugin to version 5.4.2 or later which includes the missing permission check. If unable to upgrade immediately, restrict Overall/Read permission to trusted users only.

Recommended fix High confidence

5.4.2

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Updates' tab
  4. Locate the 'Datadog Plugin' in the list
  5. Select the Datadog Plugin and click 'Download now and install after restart'
  6. Wait for the plugin to update to version 5.4.2 or later
  7. Restart Jenkins if required to complete the installation
  8. Verify the installed version is 5.4.2 or higher under 'Manage Plugins' > 'Installed' tab

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Datadog Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37944 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data