# CVE-2022-38168: Auth bypass in n/a

> Remote unauthenticated attackers can bypass login, access sensitive data, and reset passwords via URL modification in Avaya Scopia Pathfinder devices.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2022
- **Updated:** 2 May 2025
- **Also known as:** GHSA-4cwx-87j2-xc8v

## What is CVE-2022-38168?

CVE-2022-38168 is a critical authentication bypass vulnerability in n/a, published on 3 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Broken Access Control in User Authentication in Avaya Scopia Pathfinder 10 and 20 PTS version 8.3.7.0.4 allows remote unauthenticated attackers to bypass the login page, access sensitive information, and reset user passwords via URL modification.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-38168?

It affects 2 products.


Products: Avaya Scopia Pathfinder 10 Pts Firmware, Avaya Scopia Pathfinder 20 Pts Firmware.

## How do I fix CVE-2022-38168?

No fix has been published for CVE-2022-38168 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-38168 being exploited?

There is no known exploitation of CVE-2022-38168 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38168 and fix it if it is affected.

What it is: CVE-2022-38168 is a critical authentication bypass vulnerability in n/a, published on 3 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38168 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-38168/ (Markdown: https://insights.sbomify.com/CVE-2022-38168/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-38168
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-38168
- OSV: https://osv.dev/vulnerability/CVE-2022-38168

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-38168/
Summaries are generated and may contain mistakes; the official description above is the record.