dbcve.org
ItopApplication · Combodo

CVE-2024-51739

MEDIUM · 5.3 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 →
62/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. Unauthenticated user can perform users enumeration, which can make it easier to bruteforce a valid account. As a fix the sentence displayed after resetting password no longer shows if the user exists or not. This fix is included in versions 2.7.11, 3.0.5, 3.1.2, and 3.2.0. Users are advised to upgrade. Users unable to upgrade may overload the dictionary entry `"UI:ResetPwd-Error-WrongLogin"` through an extension and replace it with a generic message.

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

In Combodo iTop versions prior to 2.7.11, 3.0.5, 3.1.2, and 3.2.0, the password reset functionality reveals whether a username exists in the system. An unauthenticated attacker can submit password reset requests and observe the response to determine valid usernames, enabling subsequent brute-force attacks against those accounts.

MitigationUpgrade to iTop version 2.7.11, 3.0.5, 3.1.2, or 3.2.0. Alternatively, overload the dictionary entry 'UI:ResetPwd-Error-WrongLogin' through an extension to display a generic message regardless of user existence.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
    Check the version file in your iTop installation directory, typically in a 'version.info' file or by accessing the iTop welcome page which displays the version number
    Affected if The installed version is prior to 2.7.11, or is 3.0.0 through 3.0.4, or is 3.1.0 through 3.1.1, or is any version below 3.2.0 from the 3.x branch
  2. Locate the password reset endpoint
    Access the password reset URL path, typically at '/pages/UI.php?loginop=reset_pwd' or similar path under your iTop web root
    Affected if The password reset page is accessible without authentication
  3. Test password reset response for non-existent user
    Submit a password reset request using a clearly invalid username (e.g., 'nonexistentuser12345') and capture the HTTP response or error message
    Affected if The response indicates the user does not exist with a specific error message
  4. Test password reset response for valid user
    Submit a password reset request using a known valid username in your iTop system and capture the response
    Affected if The response differs from the invalid user response, confirming the system reveals user existence through different messages

You are affected if your iTop version falls within the vulnerable ranges and the password reset endpoint returns different responses for valid versus invalid usernames, allowing user enumeration.

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 to iTop version 2.7.11, 3.0.5, 3.1.2, or 3.2.0. Alternatively, overload the dictionary entry 'UI:ResetPwd-Error-WrongLogin' through an extension to display a generic message regardless of user existence.

Recommended fix High confidence

3.2.0 (or nearest fixed version: 2.7.11, 3.0.5, 3.1.2)

  1. 1. Back up your iTop database and configuration files before upgrading.
  2. 2. Download the appropriate fixed version for your current installation branch: 2.7.11, 3.0.5, 3.1.2, or 3.2.0.
  3. 3. Extract the new version files to your web server document root.
  4. 4. Copy your existing `config.php` and any custom extension directories to the new installation.
  5. 5. Run the iTop setup/upgrade process by accessing the setup page in your browser.
  6. 6. Follow the on-screen prompts to complete the database upgrade.
  7. 7. Verify the password reset functionality no longer reveals whether a user exists by testing with valid and invalid usernames.
Caveat Review iTop release notes for breaking changes between your current version and target upgrade version before proceeding

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

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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