dbcve.org
CheckmarxApplication · Jenkins

CVE-2022-46684

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 2022.4.3 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 Checkmarx Plugin 2022.3.3 and earlier does not escape values returned from the Checkmarx service API before inserting them into HTML reports, resulting in a stored cross-site scripting (XSS) vulnerability.

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 Checkmarx Plugin versions 2022.3.3 and earlier fail to sanitize output from the Checkmarx service API before rendering it into HTML reports. This allows malicious script content stored in Checkmarx scan results to execute in the browsers of users viewing these reports, constituting a stored XSS vulnerability.

MitigationUpgrade Jenkins Checkmarx Plugin to version 2022.3.4 or later. If immediate upgrade is not possible, restrict access to Checkmarx scan results and sanitize any existing reports until the patch can be applied.

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
CheckmarxApplication
Affected:< 2022.4.3

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 Checkmarx Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Checkmarx', or run: jenkins-plugin-cli --list-plugins | grep -i checkmarx
    Affected if Checkmarx Plugin appears in the installed plugins list
  2. Check installed Checkmarx Plugin version
    In the Installed plugins list, note the version column for Checkmarx Plugin. Alternatively, check the plugin's manifest file in JENKINS_HOME/plugins/checkmarx/META-INF/MANIFEST.MF
    Affected if Version is 2022.3.3 or earlier (any version less than 2022.4.3)
  3. Confirm Checkmarx scan results exist
    Browse to job directories containing Checkmarx scan data, typically under JENKINS_HOME/jobs/JOB_NAME/checkmarx/ or check the Checkmarx trends section in job pages
    Affected if Any Checkmarx scan results or reports are stored in Jenkins
  4. Identify HTML report access
    Check if users have access to view Checkmarx scan result reports through the Jenkins web interface (typically at job/checkmarx/ URL paths)
    Affected if HTML report viewing is enabled and accessible to users

If the Checkmarx Plugin version is below 2022.4.3 and Checkmarx scan results are present and viewable in Jenkins, the environment is vulnerable to stored XSS attacks via malicious script content in scan results.

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 2022.4.3 or later
Fixed in 2022.4.3
Interim mitigation

Upgrade Jenkins Checkmarx Plugin to version 2022.3.4 or later. If immediate upgrade is not possible, restrict access to Checkmarx scan results and sanitize any existing reports until the patch can be applied.

Recommended fix High confidence

2022.4.3

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Select the 'Updates' tab
  4. Locate the Checkmarx Plugin in the list of available updates
  5. Click 'Download now and install after restart' to update the plugin
  6. Wait for the plugin to download and install
  7. Restart Jenkins to complete the installation
  8. Verify the plugin version is 2022.4.3 or later by navigating to 'Manage Plugins' > 'Installed' and checking the Checkmarx Plugin version

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

Fix this in Checkmarx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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