CVE-2021-38117 is a high severity (CVSS 8.8) command injection in OpenText (formerly NetIQ) iManager 3.2.4.0000. A network user with low privileges could reach high impact. The vendor release notes for iManager 3.2 SP5 (August 2021) say it resolves this CVE, so upgrade to SP5 or later.
What's affected
- OpenText iManager 3.2.4.0000, per the NVD record.
- The iManager 3.2 SP5 release notes list CVE-2021-38117 among the security issues resolved.
- The record lists CWE-94 and CWE-77, covering code injection and command injection, with high impact on confidentiality, integrity and availability.
- A low privilege login is required. KEV status: false.
- The vendor gives no further technical detail, so we do not describe the vulnerable function.
How to check if you're exposed
Read the iManager version from the interface. Version 3.2.4.0000 is in the record, and the release notes mark SP5 as the fix.
Also review iManager exposure: it is a web console, so look at which networks can reach it and who holds accounts.
What to do now
- Upgrade to iManager 3.2 SP5 or later and test your administrative workflows afterwards.
- Limit network reach to the console, for example with a management VLAN or allow list.
- Remove accounts you do not need and enforce strong authentication for those that remain.
- Patch CVE-2021-38116 and CVE-2021-38118 in the same change.
- Keep a note of the iManager version in your asset inventory so future advisories are quick to match.
- Check the vendor documentation for the upgrade order if you run iManager in a container or on several servers.
Why it matters
The record lists CWE-94, improper control of code generation, together with CWE-77, command injection. Both describe input that ends up being treated as instructions. When that happens in a server side web console, the attacker can run actions with the power of the service account.
The pattern here is a cluster: several iManager CVEs fixed together. When a vendor releases a service pack with a cluster of fixes, it is usually a sign that internal review found related weaknesses. Taking the whole service pack is simpler and safer than picking single fixes.
If you cannot upgrade soon, reduce exposure first. Move the console behind a management network, require strong authentication, and review accounts. These steps do not replace the fix, but they shorten the window in which a low privilege account is enough to cause damage.
Quick check
Do I need valid credentials?
The record says low privileges are required, so yes, some account is needed.
Is there a workaround?
The sources we read do not describe one. Upgrade to 3.2 SP5 or later and restrict access to the console.
Sources
Last reviewed: 19 October 2026.