dbcve.org
ItopApplication · Combodo

CVE-2024-32870

MEDIUM · 5.8 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 2.7.11 / 3.0.5 or later.
See remediation →
67/100
Remediation priority · Elevated
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
Combodo iTop is a simple, web based IT Service Management tool. Server, OS, DBMS, PHP, and iTop info (name, version and parameters) can be read by anyone having access to iTop URI. This issue has been patched in versions 2.7.11, 3.0.5, 3.1.2, and 3.2.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

This is an information disclosure vulnerability in Combodo iTop where unauthenticated users can access sensitive system configuration details (server OS, database type, PHP version, iTop version and parameters) simply by accessing the iTop URI. The exposed information could aid attackers in further reconnaissance and targeting of the system.

MitigationUpgrade iTop to one of the patched versions (2.7.11, 3.0.5, 3.1.2, or 3.2.0). No workarounds exist for this vulnerability.

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
ItopApplication
Affected:< 2.7.11>= 3.0.0, < 3.0.5>= 3.1.0, < 3.1.2

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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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. Identify installed iTop version
    Locate the version file or check the application header/footer for the version number. Common locations include a version.php file in the application root or the about page in the web interface.
    Affected if The installed version falls within < 2.7.11, >= 3.0.0 and < 3.0.5, or >= 3.1.0 and < 3.1.2
  2. Confirm vulnerability trigger URI
    Access the iTop base URL without authentication and inspect the response for exposed system information such as server OS, database type, PHP version, iTop version, and configuration parameters.
    Affected if Sensitive system configuration details (OS, database type, PHP version, iTop version, parameters) are visible in the response without providing any credentials
  3. Check if unauthenticated access is possible
    Attempt to access the iTop application from a browser or HTTP client without logging in. Observe whether configuration details are returned automatically.
    Affected if The system returns configuration information to unauthenticated users upon simple HTTP request to the iTop URI

If the installed iTop version is less than 2.7.11, between 3.0.0-3.0.4, or between 3.1.0-3.1.1, and the application returns system configuration details to unauthenticated users, the environment is affected by CVE-2024-32870.

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 2.7.11 / 3.0.5 / 3.1.2 or later
Fixed in 2.7.113.0.53.1.2
Interim mitigation

Upgrade iTop to one of the patched versions (2.7.11, 3.0.5, 3.1.2, or 3.2.0). No workarounds exist for this vulnerability.

Recommended fix High confidence

Upgrade to iTop 3.2.0 (or the latest 3.x release appropriate for your branch - 2.7.11 for 2.x, 3.0.5 for 3.0.x, or 3.1.2 for 3.1.x)

  1. 1. Create a complete backup of the iTop database
  2. 2. Create a backup of the entire iTop installation directory
  3. 3. Download the fixed version (3.2.0 or the latest 3.x release for your branch) from the official Combodo source
  4. 4. Review the official iTop upgrade documentation for your specific version migration path
  5. 5. Upload the new files to your iTop installation, preserving the configuration file (datamodel(iTop)/config.php)
  6. 6. Run the iTop upgrade wizard by accessing the iTop URL in a web browser
  7. 7. Verify the version number reflects the fixed release in the iTop administration interface
  8. 8. Test that the iTop portal and core functionality are working correctly
Caveat No breaking changes documented in the CVE; however, always test upgrades in a staging environment before production deployment

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

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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