dbcve.org
Report PortalApplication · Jenkins

CVE-2023-30525

HIGH · 8.8 CVSS v3.1 Published 2023-04-12
Fix available
A fix is available. Upgrade to after 0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 cross-site request forgery (CSRF) vulnerability in Jenkins Report Portal Plugin 0.5 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified bearer token authentication.

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

This is a CSRF vulnerability in Jenkins Report Portal Plugin v0.5 and earlier that allows authenticated attackers to trick Jenkins into making arbitrary HTTP requests to attacker-specified URLs with attacker-controlled bearer token authentication. This enables unauthorized data exfiltration or actions against third-party services via the compromised Jenkins instance.

MitigationUpdate Jenkins Report Portal Plugin to a patched version beyond 0.5, or remove the plugin if unused. Review the plugin's authentication configuration and monitor for suspicious outbound connections.

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
Report PortalApplication
Affected:<= 0.5

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if Report Portal Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Report Portal' or check the plugin directory directly if you have CLI access
    Affected if The plugin appears in the installed plugins list
  2. Check installed version of Report Portal Plugin
    In Jenkins plugin manager, view the version of the Report Portal plugin. If using CLI, check $JENKINS_HOME/plugins/report-portal-plugin/META-INF/MANIFEST.MF for the Plugin-Version attribute
    Affected if The installed version is 0.5 or any version earlier than 0.5
  3. Verify if plugin is actively configured
    Check Jenkins job configurations or global Jenkins settings for Report Portal plugin configuration. Look for Report Portal endpoint URLs, project keys, or authentication tokens configured in job build steps or global configuration
    Affected if The plugin has an active Report Portal endpoint URL configured in any job or in Jenkins global configuration
  4. Check for CSRF protection settings
    In Jenkins, go to Manage Jenkins > Configure Global Security and examine the CSRF Protection settings. The vulnerability exploits the Jenkins CSRF protection mechanism
    Affected if CSRF protection is enabled but the plugin does not properly implement crumb validation for its API endpoints

Your environment is affected if Jenkins has Report Portal Plugin version 0.5 or earlier installed AND the plugin is actively configured with a Report Portal endpoint URL, allowing authenticated attackers to trigger arbitrary HTTP requests with attacker-controlled bearer tokens.

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 a release after 0.5
Interim mitigation

Update Jenkins Report Portal Plugin to a patched version beyond 0.5, or remove the plugin if unused. Review the plugin's authentication configuration and monitor for suspicious outbound connections.

Recommended fix Moderate confidence

Upgrade to the latest available version of Report Portal Plugin (version > 0.5)

  1. Check the Jenkins Plugin Manager for the latest version of the Report Portal Plugin
  2. Navigate to Manage Jenkins > Manage Plugins > Installed
  3. Locate Report Portal Plugin and note the current version
  4. If the installed version is 0.5 or earlier, proceed to update
  5. Click 'Check now' to fetch the latest plugin updates from the Jenkins update center
  6. Select the Report Portal Plugin and click 'Download now and install after restart'
  7. After Jenkins restarts, verify the new version is installed under Manage Plugins > Installed

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

Fix this in Report Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30525 — 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-30525 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