dbcve.org
ImanagerApplication · Microfocus

CVE-2024-3484

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-15
Fix available
A fix is available. Upgrade to 3.2.6 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
Path Traversal found in OpenText™ iManager 3.2.6.0200. This can lead to privilege escalation or file disclosure.

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

A path traversal vulnerability in OpenText iManager 3.2.6.0200 allows attackers to manipulate file paths using '../' sequences to escape restricted directories, potentially accessing sensitive system files or achieving privilege escalation.

MitigationApply available patches or updates from OpenText for iManager; until patched, restrict network access to the iManager interface and monitor for suspicious path-based requests.

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
ImanagerApplication
Affected:>= 3.0, < 3.2.6= 3.2.6

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. Confirm OpenText iManager is installed
    Check if the iManager web application is running by accessing the iManager login page (typically at /imanager or /nps) or by querying running web services on the server
    Affected if iManager is present in the environment
  2. Identify installed iManager version
    Access the iManager About page (usually via Help > About in the web interface) or check version files in the installation directory if local access is available
    Affected if version cannot be determined or is 3.0 through 3.2.6 inclusive
  3. Compare version against affected range
    Review the identified version number against the affected range: version 3.0 through version 3.2.6 (inclusive) are vulnerable
    Affected if installed version is 3.0 <= version < 3.2.6 OR version equals 3.2.6 exactly
  4. Verify web interface accessibility
    Confirm the iManager web interface is network-accessible (check firewall rules, reverse proxy configurations, or listening ports)
    Affected if iManager is exposed and version falls within affected range

If OpenText iManager is installed and the running version is 3.0 through 3.2.6 inclusive, the environment is vulnerable to path traversal attacks via the affected component.

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

Apply available patches or updates from OpenText for iManager; until patched, restrict network access to the iManager interface and monitor for suspicious path-based requests.

Recommended fix Moderate confidence

OpenText iManager 3.2.7 or later

  1. 1. Identify the current installed version of OpenText iManager by accessing the iManager web interface or checking system documentation.
  2. 2. Download the latest version of OpenText iManager from the official OpenText support portal or vendor website.
  3. 3. Review the upgrade documentation and release notes for version 3.2.7 or later to confirm the security fix for CVE-2024-3484 is included.
  4. 4. Perform a complete backup of the iManager configuration, database, and any custom settings before proceeding with the upgrade.
  5. 5. Stop all iManager services and related processes to ensure a clean upgrade environment.
  6. 6. Run the upgrade installer for the new version (3.2.7 or later), following the vendor's documented upgrade procedure.
  7. 7. After installation, verify that the upgrade was successful by checking the iManager version in the web interface.
  8. 8. Validate that the path traversal vulnerability is resolved by testing that file access is properly restricted to authorized directories.
Caveat Review release notes for potential changes to functionality, plugins, or compatibility with other OpenText/Micro Focus products before upgrading

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

Fix this in Imanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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