dbcve.org
JacocoApplication · Jenkins

CVE-2023-28669

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-02
Fix available
A fix is available. Upgrade to after 3.3.2 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 JaCoCo Plugin 3.3.2 and earlier does not escape class and method names shown on the UI, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control input files for the 'Record JaCoCo coverage report' post-build action.

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

Jenkins JaCoCo Plugin versions 3.3.2 and earlier fail to escape class and method names when rendering JaCoCo coverage reports in the UI. This allows injection of malicious JavaScript through specially crafted JaCoCo XML coverage report files, resulting in a stored XSS vulnerability when users view the affected coverage results.

MitigationUpdate Jenkins JaCoCo Plugin to a version that properly escapes class and method name output. Until then, restrict access to users who can configure or trigger jobs with the 'Record JaCoCo coverage report' post-build action.

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
JacocoApplication
Affected:<= 3.3.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
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. Check Jenkins JaCoCo Plugin version
    Go to Manage Jenkins > Manage Plugins > Installed tab, locate 'JaCoCo' plugin in the list and note the version number under the 'Version' column
    Affected if Version is 3.3.2 or earlier
  2. Identify jobs using JaCoCo coverage recording
    In Jenkins, go to each job's configuration and check if the 'Record JaCoCo coverage report' post-build action is enabled. Alternatively, search for jobs containing 'jacoco' in their config.xml files in $JENKINS_HOME/jobs/
    Affected if Any job has the JaCoCo post-build action configured
  3. Verify XML coverage report processing
    Inspect the JaCoCo plugin's behavior when displaying coverage reports: when a user views coverage results (typically via 'Coverage Report' link on job pages), the class and method names from the XML are rendered in the UI without escaping
    Affected if Users can view JaCoCo coverage reports and the plugin renders class/method names directly in HTML
  4. Assess user access to trigger vulnerable jobs
    Review which users have permissions to either configure jobs with JaCoCo or trigger builds that produce JaCoCo coverage reports. Check job-level permissions and any matrix authorization settings
    Affected if Users with job configure or build permissions exist who could inject malicious XML content

You are affected if the JaCoCo Plugin version is 3.3.2 or earlier AND any job is configured to record JaCoCo coverage reports that users can view.

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 3.3.2
Interim mitigation

Update Jenkins JaCoCo Plugin to a version that properly escapes class and method name output. Until then, restrict access to users who can configure or trigger jobs with the 'Record JaCoCo coverage report' post-build action.

Recommended fix Moderate confidence

JaCoCo Plugin version 3.3.3 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Select the 'Installed' tab
  3. Locate the 'JaCoCo' plugin in the list
  4. If an update is available, select it and click 'Download now and install after restart'
  5. Restart Jenkins to complete the plugin update

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

Fix this in Jacoco Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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