# CVE-2022-23173: Priority - Priority web Insecure direct object references (IDOR)

> Attackers can bypass authorization controls by modifying a parameter to access restricted functionality in the Priority web application.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g4qr-pvvg-9h2w

## What is CVE-2022-23173?

CVE-2022-23173 is a medium-severity missing authorization vulnerability in Priority web, published on 6 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

this vulnerability affect user that even not allowed to access via the web interface. First of all, the attacker needs to access the "Login menu - demo site" then he can see in this menu all the functionality of the application. If the attacker will try to click on one of the links, he will get an answer that he is not authorized because he needs to log in with credentials. after he performed log in to the system there are some functionalities that the specific user is not allowed to perform because he was configured with low privileges however all the attacker need to do in order to achieve his goals is to change the value of the prog step parameter from 0 to 1 or more and then the attacker could access to some of the functionality the web application that he couldn't perform it before the parameter changed.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Priority-Software Priority.

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

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

## Is CVE-2022-23173 being exploited?

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

## Other vulnerabilities in Priority web

- [CVE-2023-23459](https://insights.sbomify.com/CVE-2023-23459/): Priority Windows – Command Execution via SQL Injection (critical 9.1)
- [CVE-2023-23460](https://insights.sbomify.com/CVE-2023-23460/): Priority Web – Authentication bypass (critical 9.1)
- [CVE-2024-41697](https://insights.sbomify.com/CVE-2024-41697/): Priority – CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (medium 6.1)
- [CVE-2022-23172](https://insights.sbomify.com/CVE-2022-23172/): Priority - Priority User Enumeration (medium 5.5)
- [CVE-2024-41699](https://insights.sbomify.com/CVE-2024-41699/): Priority – CWE-552: Files or Directories Accessible to External Parties (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23173 is a medium-severity missing authorization vulnerability in Priority web, published on 6 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23173 in the wild and no public exploit code.

Affected product: Priority web. 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-23173/ (Markdown: https://insights.sbomify.com/CVE-2022-23173/index.md)
```

## Sources

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

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