CVE-2022-22572
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 · uneditedA non-admin user with user management permission can escalate his privilege to admin user via password reset functionality. The vulnerability affects Incapptic Connect version < 1.40.1.
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 confidenceA vertical privilege escalation exists in Incapptic Connect where a non-admin user possessing user management permissions can elevate their account to admin-level access through the password reset mechanism. The password reset functionality fails to properly validate authorization boundaries, allowing a user with limited permissions to modify their own account privileges during the reset process.
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< 1.40.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Incapptic Connect versionCheck the installed version of Ivanti Incapptic Connect through the application UI admin panel, command-line interface, or product documentation. Common locations include the About section in the web interface, a version file in the installation directory, or the product release information.Affected if The installed version is any release prior to 1.40.2 (for example, 1.40.1, 1.40.0, or earlier)
-
Verify user management permissions existReview the role-based access control configuration in Incapptic Connect to identify whether any non-admin user accounts have been granted user management or user administration permissions.Affected if Non-admin users exist with assigned user management permissions
-
Confirm password reset functionality is accessibleTest whether the password reset mechanism is accessible to authenticated non-admin users with user management permissions. Log in as a non-admin user with such permissions and attempt to access or use the password reset feature.Affected if Non-admin users with user management permissions can access the password reset functionality
-
Check for unauthorized privilege changesAudit account modification logs, privilege change logs, or admin access logs to identify any instances where non-admin accounts have been elevated to administrator-level access, particularly in correlation with password reset operations.Affected if Any non-admin account with user management permissions has been modified to gain admin-level access
A user is affected if running Incapptic Connect version below 1.40.2 and non-admin accounts with user management permissions can access the password reset mechanism, allowing them to escalate their own privileges to admin level.
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 · scoped1.40.2
Upgrade to Incapptic Connect version 1.40.1 or later, which contains the fix for this vulnerability. Additionally, audit the password reset functionality to ensure proper authorization validation prevents privilege escalation.
1.40.2 or later
- Identify the current Incapptic Connect version running in your environment
- Create a complete backup of the Incapptic Connect installation and associated data
- Upgrade Incapptic Connect to version 1.40.2 or later
- After upgrade, verify that non-admin users with user management permissions can no longer escalate privileges to admin via password reset
- Confirm the upgrade was successful by checking the version number in the administration interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22572 — 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-22572 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