dbcve.org
ImanagerApplication · Microfocus

CVE-2024-3485

HIGH · 7.5 CVSS v3.1 Published 2024-05-15
Fix available
A fix is available. Upgrade to 3.2.6 or later.
See remediation →
84/100
Remediation priority · High
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
Server Side Request Forgery vulnerability has been discovered in OpenText™ iManager 3.2.6.0200. This could lead to senstive information 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

Server-Side Request Forgery (SSRF) vulnerability in OpenText iManager 3.2.6.0200 allows attackers to induce the server to make arbitrary requests to internal or external resources, potentially exposing sensitive internal services, metadata endpoints, or network infrastructure information.

MitigationApply vendor-provided patches for OpenText iManager; implement URL allowlisting and input validation to restrict server-side requests to trusted destinations.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Determine installed iManager version
    Check the product version displayed in the iManager web interface (typically on the login page or in Help > About), or inspect version files in the installation directory if you have server access
    Affected if The installed version is 3.0 through 3.2.5 inclusive, or exactly 3.2.6. Versions below 3.0 or above 3.2.6 are not affected.
  2. Verify iManager web interface is exposed
    Confirm that the iManager web application is accessible over HTTP/HTTPS. This vulnerability is exploitable only if the web interface is reachable by an attacker
    Affected if The iManager web portal is externally or internally accessible without sufficient network segmentation.
  3. Check for URL-related request parameters
    If you have access to application logs or can review the application code, identify endpoints that accept URL or URI parameters and could be manipulated to make server-side requests
    Affected if The application accepts user-supplied URLs in any parameter without proper validation or allowlisting.
  4. Inspect HTTP access logs for suspicious internal requests
    Review iManager HTTP server logs for requests to internal IP addresses (127.0.0.1, 10.x.x.x, 192.168.x.x), cloud metadata endpoints (169.254.169.254), or unusual internal hostnames originating from the server itself
    Affected if Logs show the server making outbound requests to internal infrastructure or cloud metadata services that were not initiated by legitimate administrative actions.

Your environment is affected if OpenText iManager version 3.0 through 3.2.6 is installed and the web interface is accessible to potential attackers who could exploit the SSRF vulnerability.

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 vendor-provided patches for OpenText iManager; implement URL allowlisting and input validation to restrict server-side requests to trusted destinations.

Recommended fix Moderate confidence

iManager 3.2.7 or later

  1. Download the latest iManager version from the NetIQ/OpenText support portal
  2. Review upgrade documentation for iManager 3.2.x
  3. Backup the current iManager installation and database
  4. Install the updated iManager version (3.2.7 or later)
  5. Verify the SSRF vulnerability is resolved by testing the affected endpoint
  6. Confirm all iManager services start successfully post-upgrade
Caveat Review release notes for any deprecated features or configuration changes between 3.2.6 and the target upgrade version

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

Fix this in Imanager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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