CVE-2021-21406
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 · uneditedCombodo iTop is an open source, web based IT Service Management tool. In versions prior to 2.7.4, there is a command injection vulnerability in the Setup Wizard when providing Graphviz executable path. The vulnerability is patched in version 2.7.4 and 3.0.0.
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 confidenceCommand injection vulnerability in Combodo iTop's Setup Wizard when providing the Graphviz executable path allows attackers to execute arbitrary commands. The vulnerability affects versions prior to 2.7.4 and is patched in versions 2.7.4 and 3.0.0.
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< 2.7.4= 2.7.5= 2.7.5-1CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed iTop versionLocate the version file in the iTop web root or configuration directory and extract the version numberAffected if Installed version is less than 2.7.4, or is exactly 2.7.5 or 2.7.5-1
-
Check if Setup Wizard is accessibleVerify whether the Setup Wizard directory or entry point remains on the web server and is reachable via HTTP/HTTPSAffected if Setup Wizard is present and accessible in the production environment
-
Confirm Graphviz configuration exposureInspect the Setup Wizard or related configuration files to determine if the Graphviz executable path setting is exposed and can be manipulatedAffected if Graphviz path can be configured through the Setup Wizard interface
You are affected if your iTop version falls within the vulnerable range AND the Setup Wizard remains accessible with the Graphviz path configuration feature available.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.7.4
Upgrade to iTop version 2.7.4, 3.0.0, or later. Until patched, restrict access to the Setup Wizard and ensure it cannot be reached in production environments.
iTop 3.0.0 (recommended) or iTop 2.7.5-1
- 1. Back up your iTop installation and database before upgrading.
- 2. Download the latest stable version of iTop from the official source (https://www.itop-itsm.org/).
- 3. If using iTop 2.x line, ensure you upgrade to version 2.7.5-1 or later which contains the command injection fix.
- 4. Alternatively, upgrade to iTop 3.0.0 which also contains the fix for this vulnerability.
- 5. After upgrading, verify the Setup Wizard Graphviz executable path setting works correctly.
- 6. Confirm the upgrade by checking the iTop version in the administration console.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21406 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-21406 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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