dbcve.org
ImanagerApplication · Microfocus

CVE-2024-4429

HIGH · 7.4 CVSS v3.1 Published 2024-05-28
Fix available
A fix is available. Upgrade to 3.2.6 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges

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
Cross-Site Request Forgery vulnerability has been discovered in OpenText™ iManager 3.2.6.0200. This could lead to sensitive 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

A Cross-Site Request Forgery (CSRF) vulnerability in OpenText iManager 3.2.6.0200 allows attackers to trick authenticated users into performing unintended actions, potentially leading to disclosure of sensitive information. The lack of proper CSRF tokens or anti-CSRF measures enables malicious requests to be crafted on behalf of legitimate users.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and configure SameSite cookie attributes. Additionally, implement proper referer validation and consider adding confirmation dialogs for sensitive actions.

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
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Identify iManager version
    Access the iManager admin interface and navigate to Help > About, or check the login page footer/version endpoint for the installed version number
    Affected if The version is 3.0 through 3.2.6 inclusive (any version >= 3.0 but < 3.2.6, or exactly 3.2.6)
  2. Verify web interface is accessible
    Confirm you can reach the iManager login page (typically /nps/imanager.html or similar) in a browser
    Affected if The web interface is exposed and accessible to users
  3. Inspect forms for CSRF tokens
    Log into iManager, navigate to a state-changing function (such as user creation, group management, or server configuration), view the page source or use browser dev tools to inspect forms
    Affected if Forms lack hidden CSRF token fields (such as csrfToken, csrftoken, or similar) and rely solely on session cookies
  4. Check cookie SameSite attributes
    In browser dev tools, go to Application > Cookies for the iManager domain, inspect the session cookie and check if SameSite attribute is set
    Affected if The session cookie lacks SameSite attribute or has SameSite=None without Secure flag
  5. Test anti-CSRF Referer validation
    Submit a state-changing request with a mismatched or missing Referer header using a tool like Burp Suite or curl, observe if the request is rejected
    Affected if Requests with invalid or missing Referer headers are accepted without rejection

Your environment is affected if iManager version is between 3.0 and 3.2.6 inclusive AND the web interface is accessible AND forms lack CSRF token protection.

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

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and configure SameSite cookie attributes. Additionally, implement proper referer validation and consider adding confirmation dialogs for sensitive actions.

Recommended fix Moderate confidence

iManager version > 3.2.6 (contact NetIQ/OpenText for exact latest fixed release)

  1. 1. Identify the current installed version of OpenText iManager by checking the application or system documentation
  2. 2. Navigate to the NetIQ/OpenText support portal at www.netiq.com to obtain the latest security patch or updated version
  3. 3. Download the fixed version of iManager (version higher than 3.2.6) that addresses the CVE-2024-4429 CSRF vulnerability
  4. 4. Review the upgrade documentation and release notes for any specific migration or pre-upgrade requirements
  5. 5. Create a complete backup of the current iManager configuration and database
  6. 6. Schedule a maintenance window to perform the upgrade
  7. 7. Apply the upgrade following the documented installation procedures
  8. 8. After upgrade, verify the iManager web interface is functioning correctly
Caveat Review release notes for potential configuration changes or compatibility impacts before upgrading

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

Fix this in Imanager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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