CVE-2022-26329
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 · uneditedFile existence disclosure vulnerability in NetIQ Identity Manager plugin prior to version 4.8.5 allows attacker to determine whether a file exists on the filesystem. This issue affects: Micro Focus NetIQ Identity Manager NetIQ Identity Manager versions prior to 4.8.5 on ALL.
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 confidenceNetIQ Identity Manager plugin before version 4.8.5 contains a file existence disclosure vulnerability that allows remote attackers to determine whether specific files exist on the filesystem via the plugin's interface. This information disclosure could aid attackers in reconnaissance efforts to map system paths and identify sensitive files.
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< 4.8.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm NetIQ Identity Manager plugin installationLocate the NetIQ Identity Manager plugin installation directory and identify the installed version number using the product's standard version check method (typically via the product's admin console, version info file, or package management system)Affected if The plugin is present but the version is below 4.8.5
-
Compare installed version against the fixed releaseReview the identified version number and compare it to 4.8.5, noting that any version lower than 4.8.5 is affectedAffected if Installed version is less than 4.8.5 (for example, 4.8.0, 4.7.x, or any 4.x release below 4.8.5)
-
Verify plugin management interface accessibilityDetermine if the NetIQ Identity Manager plugin's web or API interface is exposed to network access, as the vulnerability is exploited through this interfaceAffected if The plugin interface is network-accessible and the installed version is below 4.8.5
A user is affected if NetIQ Identity Manager plugin version is below 4.8.5 and the plugin interface is accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.8.5
Upgrade NetIQ Identity Manager plugin to version 4.8.5 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the plugin's management interfaces to reduce attack surface.
4.8.5
- Obtain NetIQ Identity Manager version 4.8.5 from the official Micro Focus/NetIQ download portal
- Follow the standard NetIQ Identity Manager upgrade procedure to install version 4.8.5
- Verify the upgrade was successful and the version is now 4.8.5 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26329 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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