CVE-2022-43890 is a medium severity (CVSS 5.3) information disclosure in IBM Security Verify Privilege On-Premises 11.5 and earlier. An HTTP request could reveal internal product details that help an attacker. IBM publishes a fix for version 11.5, so apply it and confirm the details in the bulletin.
What's affected
IBM's bulletin lists IBM Security Verify Privilege On-Premises 11.5 and earlier as affected, and describes the problem as an application error that discloses internal product details. The remediation reads "Fixed in 11.5 version onward" and links an interim fix identified as 11.5-ISV-PV-11.5.000002. The bulletin lists no workarounds.
That wording is slightly odd, since version 11.5 appears on both the affected and the fixed side. The sensible reading is that 11.5 needs the named interim fix applied, but confirm that with IBM before you close the ticket. The record also lists the product as the on-premises 11.5 release.
The record scores the flaw 5.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, and IBM's bulletin gives the same score. The class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor).
How to check if you're exposed
Check the installed version of IBM Security Verify Privilege On-Premises in your appliance or deployment records, and check whether the interim fix named in the bulletin has been applied. IBM's fix identifier is 11.5-ISV-PV-11.5.000002.
If you cannot tell whether the fix is applied, ask IBM support to confirm for your build. The bulletin also mentions that several vulnerabilities in which internal product details were disclosed were remediated, so the fix may be part of a wider set.
What to do now
- Confirm the version and fix level of every Verify Privilege On-Premises instance.
- Download and apply the interim fix named in IBM's bulletin, then confirm the result with IBM support if the wording is unclear.
- Limit network access to the product's web interface to the networks that need it.
- Review how error messages are handled by any reverse proxy in front of the product, and avoid passing raw application errors to outside users.
Why it matters
An application error page that shows internal details is a gift to an attacker doing reconnaissance. Version strings, paths and component names narrow down which known weaknesses to try. The record places this in the sensitive information exposure class and scores it medium because nothing is changed or taken directly.
The product is a privileged access tool, which means it guards the most powerful accounts in a company. Even a low impact leak from a system like that deserves a prompt fix, because a defender wants the least possible information visible about the control point. The record's KEV flag is false and the bulletin does not report exploitation.
Quick check
Why is the fixed version unclear?
The bulletin lists 11.5 and earlier as affected and says fixed in 11.5 onward, with a named interim fix. Confirm the exact fix level with IBM.
Is there a workaround?
The bulletin lists none.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.