# CVE-2023-4997: Improper authorisation in Uptime DC

> Regular users can change administrator passwords due to improper authorization, leading to privilege escalation in ProIntegra Uptime DC.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2023
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-hh4p-ff9x-4g5c

## What is CVE-2023-4997?

CVE-2023-4997 is a high-severity missing authorization vulnerability in ProIntegra S.A. UptimeDC, published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper authorisation of regular users in ProIntegra Uptime DC software (versions below 2.0.0.33940) allows them to change passwords of all other users including administrators leading to a privilege escalation.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-4997?

It affects 1 product.


Products: Prointegra Uptimedc.

## How do I fix CVE-2023-4997?

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

## Is CVE-2023-4997 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4997 and fix it if it is affected.

What it is: CVE-2023-4997 is a high-severity missing authorization vulnerability in ProIntegra S.A. UptimeDC, published on 4 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4997 in the wild and no public exploit code.

Affected product: ProIntegra S.A. UptimeDC. 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-2023-4997/ (Markdown: https://insights.sbomify.com/CVE-2023-4997/index.md)
```

## Sources

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

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