dbcve.org
Testng ResultsApplication · Jenkins

CVE-2022-34778

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-30
Fix available
A fix is available. Upgrade to after 554.va4a552116332 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 TestNG Results Plugin 554.va4a552116332 and earlier renders the unescaped test descriptions and exception messages provided in test results if certain job-level options are set, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers able to configure jobs or control test results.

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 TestNG Results Plugin versions 554.va4a552116332 and earlier contains a stored XSS vulnerability. The plugin renders test descriptions and exception messages from test results without proper HTML escaping when certain job-level display options are enabled. Attackers with job configuration permissions or control over test result content can inject malicious scripts that execute in the browsers of users viewing test result reports.

MitigationUpdate the TestNG Results Plugin to the latest version to receive the fix that properly escapes test descriptions and exception messages. Until patched, review and disable any affected job-level display options that render unescaped content.

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
Testng ResultsApplication
Affected:<= 554.va4a552116332

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 TestNG Results Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, locate 'TestNG Results Plugin' in the list, and verify the version column against 554.va4a552116332
    Affected if Plugin version is 554.va4a552116332 or earlier
  2. Identify jobs using TestNG plugin
    Review Jenkins jobs that publish TestNG test results, typically configured under 'Post-build Actions' with 'Publish TestNG Results'
    Affected if Any job is configured to publish TestNG results and uses the plugin
  3. Check job display options for unescaped rendering
    Examine the job configuration: look for display options related to 'Show exception messages' or 'Test description' that may render HTML without escaping in the TestNG results report
    Affected if Job-level display options that render test descriptions or exception messages are enabled and visible to other users

You are affected if the TestNG Results Plugin is installed at version 554.va4a552116332 or earlier AND any job with TestNG results has display options enabled that render test descriptions or exception messages without HTML escaping.

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 554.va4a552116332
Interim mitigation

Update the TestNG Results Plugin to the latest version to receive the fix that properly escapes test descriptions and exception messages. Until patched, review and disable any affected job-level display options that render unescaped content.

Recommended fix High confidence

TestNG Results Plugin version 556.v5a_6a_5a_6b_9d7 or later

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Click on the 'Installed' tab
  4. 4. Locate 'TestNG Results' plugin in the list
  5. 5. If an update is available, click 'Update' or upgrade to the latest version
  6. 6. Restart Jenkins if required to complete the installation

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

Fix this in Testng Results 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-34778 — 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-34778 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