dbcve.org
Testcomplete SupportApplication · Jenkins

CVE-2023-24443

CRITICAL · 9.8 CVSS v3.1 Published 2023-01-26
Fix available
A fix is available. Upgrade to after 2.8.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 TestComplete support Plugin 2.8.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.

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 TestComplete support Plugin versions 2.8.1 and earlier contains an XML External Entity (XXE) vulnerability due to its XML parser not being configured to disable external entity processing. This allows attackers to craft malicious XML payloads that can read local files on the server or cause denial-of-service conditions.

MitigationConfigure the XML parser to disable external entity processing by setting secure features such as disabling DTDs, blocking external entity access, and using secure processing settings. Upgrade to a patched version of the plugin once 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
Testcomplete SupportApplication
Affected:<= 2.8.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check TestComplete Support plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and locate 'TestComplete Support' in the list. The version column shows the installed version. Alternatively, check the plugin file timestamp or version file in the $JENKINS_HOME/plugins/testcomplete-support/ directory.
    Affected if The installed version is 2.8.1 or lower (any version up to and including 2.8.1).
  2. Verify the plugin is loaded and active
    Confirm the TestComplete Support plugin appears in Manage Jenkins > Manage Plugins > Installed as 'Enabled'. Also check that no security warning appears for this plugin in the Jenkins logs or plugin manager.
    Affected if The plugin is installed at a vulnerable version AND is enabled/loaded in Jenkins.
  3. Identify jobs using TestComplete integration
    Search job configurations for TestComplete-related build steps or publishers. Look for 'TestComplete' in job configuration pages under Build Steps or Post-build Actions, or search configuration XML files in $JENKINS_HOME/jobs/ for 'testcomplete'.
    Affected if Jobs are configured to use TestComplete functionality, which triggers the plugin's XML parsing code where the XXE vulnerability resides.

If the TestComplete Support plugin version is 2.8.1 or earlier and the plugin is enabled, the environment is vulnerable to XXE attacks when processing XML files through TestComplete build steps.

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

Configure the XML parser to disable external entity processing by setting secure features such as disabling DTDs, blocking external entity access, and using secure processing settings. Upgrade to a patched version of the plugin once available.

Recommended fix Moderate confidence

TestComplete Support Plugin version > 2.8.1 (check Jenkins plugin repository for the specific fixed version)

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate 'TestComplete Support' plugin in the list
  5. If a fixed version (greater than 2.8.1) is available, click 'Update' to upgrade
  6. Restart Jenkins if required for the update to take effect
  7. If no update is available, consider temporarily disabling the plugin until a fixed version is released

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

Fix this in Testcomplete Support 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-2023-24443 — 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-24443 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