dbcve.org
CloverdxApplication

CVE-2021-42776

HIGH · 7.7 CVSS v3.1 Published 2021-12-01
Fix available
A fix is available. Upgrade to 5.11.2 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
CloverDX Server before 5.11.2 and and 5.12.x before 5.12.1 allows XXE during configuration import.

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 · moderate confidence

CloverDX Server versions before 5.11.2 and 5.12.x before 5.12.1 are vulnerable to XML External Entity (XXE) injection during the configuration import feature. An attacker could craft a malicious XML configuration file to read arbitrary files from the server filesystem or perform server-side request forgery (SSRF) attacks.

MitigationUpgrade to CloverDX Server 5.11.2 or 5.12.1 or later. As a workaround, disable external entity resolution in the XML parser used for configuration import.

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
CloverdxApplication
Affected:< 5.11.2= 5.12.0= 5.12.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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/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 installed CloverDX Server version
    Locate the CloverDX Server installation and identify its version number (typically found in server logs, about page, or installation directory metadata). Compare it to the affected ranges: versions below 5.11.2, or exactly 5.12.0 or 5.12.1 are vulnerable.
    Affected if Your installed version is less than 5.11.2, or is exactly 5.12.0 or 5.12.1
  2. Determine if configuration import feature is accessible
    Identify whether the configuration import functionality is enabled and accessible in your CloverDX Server deployment. This feature allows importing XML-based configuration files.
    Affected if The configuration import feature is enabled and users with appropriate permissions can upload XML files
  3. Verify XML parser configuration for configuration imports
    Examine the XML parser settings used by the configuration import functionality. Check whether external entity resolution is permitted in the parser configuration.
    Affected if The XML parser allows external entity resolution (DTD or external references) for configuration file parsing
  4. Review recent configuration file imports
    Audit server logs and configuration import history to identify any suspicious or unexpected XML configuration files that were recently imported.
    Affected if Unrecognized or externally-sourced XML configuration files were imported recently

You are affected if your CloverDX Server version falls within the vulnerable range (below 5.11.2, or exactly 5.12.0 or 5.12.1) and the configuration import feature with XML parsing is enabled.

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

Upgrade to CloverDX Server 5.11.2 or 5.12.1 or later. As a workaround, disable external entity resolution in the XML parser used for configuration import.

Recommended fix High confidence

CloverDX Server 5.11.2 (or later 5.11.x) or 5.12.1 (or later 5.12.x)

  1. 1. Back up your current CloverDX Server configuration and data.
  2. 2. Download the fixed version from CloverDX support portal (5.11.2 or later for the 5.11.x branch, or 5.12.1 or later for the 5.12.x branch).
  3. 3. Stop the CloverDX Server service.
  4. 4. Install or extract the new version to your server environment.
  5. 5. Restore your configuration from the backup.
  6. 6. Start the CloverDX Server service.
  7. 7. Verify that configuration import works correctly and the XXE vulnerability is mitigated.

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

Fix this in Cloverdx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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