dbcve.org
Contrast Continuous Application SecurityApplication · Jenkins

CVE-2022-43420

MEDIUM · 5.4 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 3.10 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 Contrast Continuous Application Security Plugin 3.9 and earlier does not escape data returned from the Contrast service when generating a report, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control or modify Contrast service API responses.

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 Contrast Continuous Application Security Plugin versions 3.9 and earlier fails to properly escape or sanitize data returned from the Contrast service API when generating reports. This allows an attacker who can control or modify the Contrast service API responses to inject malicious JavaScript code that gets stored and executed when users view the generated reports.

MitigationEscape all data originating from the Contrast service API before rendering it in reports using appropriate encoding functions (e.g., Jenkins' escape methods or standard HTML encoding). Update to plugin version 3.10 or later if 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
Contrast Continuous Application SecurityApplication
Affected:< 3.10

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 the Contrast Continuous Application Security plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar get-plugins (or check /var/lib/jenkins/plugins directory)
    Affected if The plugin named 'Contrast Continuous Application Security' or 'contrast-continuous-application-security' appears in the installed plugins list
  2. Determine the installed plugin version
    In Jenkins UI: Manage Jenkins > Manage Plugins > Installed > Contrast plugin, note the Version column. Alternatively, inspect the plugin manifest: /var/lib/jenkins/plugins/contrast-continuous-application-security/META-INF/MANIFEST.MF
    Affected if The version number is 3.9 or earlier, or any version below 3.10
  3. Confirm the plugin is configured with Contrast service credentials
    Navigate to: Jenkins > Manage Jenkins > Configure System > look for 'Contrast ASS' or 'Contrast Continuous Application Security' section. Check if API credentials (API Key, API Username, Service Key) are configured and a Contrast team server URL is set
    Affected if The plugin has valid Contrast service credentials configured and is actively connecting to a Contrast service API
  4. Identify if any Contrast reports have been generated
    Look for Contrast-related build artifacts or reports in completed jobs. Check job build directories under /var/lib/jenkins/jobs/<job-name>/builds/ for Contrast report files, or view job pages for Contrast report links
    Affected if Contrast security reports have been generated and are accessible via the Jenkins UI or stored as build artifacts

You are affected if the Contrast Continuous Application Security plugin versions 3.9 or earlier is installed, configured with API credentials, and Contrast security reports have been generated - the unsanitized API response data would be rendered in those reports.

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

Escape all data originating from the Contrast service API before rendering it in reports using appropriate encoding functions (e.g., Jenkins' escape methods or standard HTML encoding). Update to plugin version 3.10 or later if available.

Recommended fix High confidence

Contrast Continuous Application Security plugin version 3.10 or later

  1. Navigate to Jenkins Manage Plugins page
  2. Go to the 'Installed' tab and find 'Contrast Continuous Application Security' plugin
  3. Click 'Update' to install the latest version, or manually download and install version 3.10 or later
  4. Restart Jenkins services if required to complete the installation
  5. Verify the plugin version is 3.10 or higher in the installed plugins list

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

Fix this in Contrast Continuous Application Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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