Red Hat Dependency AnalyticsApplication · Jenkins

CVE-2024-23905

MEDIUM · 5.4 CVSS v3.1 Published 2024-01-24
Fix available
A fix is available. Upgrade to after 0.7.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Jenkins Red Hat Dependency Analytics Plugin 0.7.1 and earlier programmatically disables Content-Security-Policy protection for user-generated content in workspaces, archived artifacts, etc. that Jenkins offers for download.

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 · high confidence

The Jenkins Red Hat Dependency Analytics Plugin version 0.7.1 and earlier programmatically disables Content-Security-Policy (CSP) protection for user-generated content in workspaces, archived artifacts, and other downloadables. This weakens Jenkins' defense-in-depth against XSS attacks by removing the CSP header that restricts script execution from untrusted sources.

MitigationUpgrade the Jenkins Red Hat Dependency Analytics Plugin to a version that no longer disables CSP protection; if no patched version exists, consider removing or disabling the plugin until a fix is available.

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
Red Hat Dependency AnalyticsApplication
Affected:<= 0.7.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Red Hat Dependency Analytics plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.collect { it.shortName }.contains('red-hat-dependency-analytics')
    Affected if The plugin appears in the installed plugins list or the script returns true
  2. Identify the installed plugin version
    In Manage Jenkins > Manage Plugins > Installed tab, locate 'Red Hat Dependency Analytics' and note the Version column; alternatively, use the script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'red-hat-dependency-analytics' }.version
    Affected if The version returned is 0.7.1 or any version lower than 0.7.1
  3. Confirm CSP header behavior in responses
    Trigger a build or access a workspace/artifact URL, then inspect HTTP response headers using browser dev tools or curl -I <url>; look for the Content-Security-Policy header
    Affected if The CSP header is missing from responses related to workspaces or archived artifacts while the plugin is enabled
  4. Check plugin configuration for CSP-related settings
    Navigate to Manage Jenkins > System > Red Hat Dependency Analytics (if a configuration section exists), or inspect the plugin's config.xml file in JENKINS_HOME/war/
    Affected if The plugin configuration explicitly disables CSP protection or removes CSP headers

A user is affected if the Red Hat Dependency Analytics Plugin version 0.7.1 or earlier is installed and enabled, resulting in missing Content-Security-Policy headers for workspaces and artifacts.

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.

From vendor data
Upgrade available Upgrade to a release after 0.7.1
Interim mitigation

Upgrade the Jenkins Red Hat Dependency Analytics Plugin to a version that no longer disables CSP protection; if no patched version exists, consider removing or disabling the plugin until a fix is available.

Fix this in Red Hat Dependency Analytics Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2024-23905 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