dbcve.org
IdentityiqApplication · Sailpoint

CVE-2022-46835

HIGH · 7.5 CVSS v3.1 Published 2023-01-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
IdentityIQ 8.3 and all 8.3 patch levels prior to 8.3p2, IdentityIQ 8.2 and all 8.2 patch levels prior to 8.2p5, IdentityIQ 8.1 and all 8.1 patch levels prior to 8.1p7, IdentityIQ 8.0 and all 8.0 patch levels prior to 8.0p6 allow access to arbitrary files in the application server filesystem due to a path traversal vulnerability in JavaServer Faces (JSF) 2.2.20 documented in CVE-2020-6950.

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 · high confidence

IdentityIQ versions 8.0-8.3 prior to specified patch levels contain a path traversal vulnerability in the bundled JavaServer Faces (JSF) 2.2.20 library, originally documented in CVE-2020-6950. This flaw allows unauthenticated attackers to access arbitrary files on the application server filesystem by manipulating file paths in JSF requests.

MitigationUpgrade IdentityIQ to version 8.0p6, 8.1p7, 8.2p5, 8.3p2 or later to incorporate the patched JSF library, or apply the vendor-supplied patch for CVE-2020-6950 to the JSF component.

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
IdentityiqApplication
Affected:= 8.0= 8.1= 8.2= 8.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 IdentityIQ version
    Check the IdentityIQ version by reviewing the identityiq.properties file typically located in the IdentityIQ WEB-INF/iiq directory, or by accessing the IdentityIQ console and viewing the About section.
    Affected if The installed version is 8.0, 8.1, 8.2, or 8.3 without the corresponding patch level (8.0p6, 8.1p7, 8.2p5, or 8.3p2).
  2. Locate bundled JSF library
    Search for JSF library files (such as jsf-impl.jar, javax.faces.jar, or mojarra*.jar) within the IdentityIQ deployment directory, typically under WEB-INF/lib or in the application server's lib folder.
    Affected if A JSF library version 2.2.20 or earlier (from the Mojarra project) is bundled with IdentityIQ.
  3. Verify JSF library version
    Inspect the manifest file or pom.properties within the JSF JAR file to determine the exact version of the bundled JSF implementation.
    Affected if The bundled JSF library is version 2.2.20 or earlier, which contains the path traversal vulnerability from CVE-2020-6950.
  4. Confirm JSF endpoints accessible
    Test whether JSF-related endpoints are exposed on the IdentityIQ application (such as /javax.faces.resource/* or similar paths). Check the web.xml deployment descriptor for JSF servlet mappings.
    Affected if JSF servlet mappings are present and accessible without authentication, allowing file path manipulation in resource requests.

A user is affected if IdentityIQ version 8.0-8.3 is running without the required patch level and the bundled JSF library (version 2.2.20 or earlier) is accessible, allowing unauthenticated path traversal attacks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade IdentityIQ to version 8.0p6, 8.1p7, 8.2p5, 8.3p2 or later to incorporate the patched JSF library, or apply the vendor-supplied patch for CVE-2020-6950 to the JSF component.

Recommended fix High confidence

Apply the appropriate patch: 8.0p6, 8.1p7, 8.2p5, or 8.3p2 (based on your current major version)

  1. Identify the currently installed IdentityIQ version (8.0, 8.1, 8.2, or 8.3)
  2. For IdentityIQ 8.0: Apply patch 8.0p6
  3. For IdentityIQ 8.1: Apply patch 8.1p7
  4. For IdentityIQ 8.2: Apply patch 8.2p5
  5. For IdentityIQ 8.3: Apply patch 8.3p2
  6. Restart the application server after applying the patch
  7. Verify the patch was successfully applied by checking the IdentityIQ version
Caveat Patches are cumulative and should not introduce breaking changes; always test in a non-production environment first

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

Fix this in Identityiq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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