# CVE-2025-3838: Improper Authorization in the installer for the EOL OVA based connect component

> Attackers can access the local database containing weakly hashed credentials due to improper authorization in the deprecated Saviynt OVA Connect installer.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2025
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-4f5w-327f-jw8g

## What is CVE-2025-3838?

CVE-2025-3838 is a medium-severity missing authorization vulnerability in Saviynt OVA based Connect, published on 21 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An Improper Authorization vulnerability was identified in the EOL OVA based connect component which is deployed for installation purposes in the customer internal network. Under certain conditions, this could allow a bad actor to gain unauthorized access to the local db containing weakly hashed credentials of the installer. This EOL component was deprecated in September 2023 with end of support extended till January 2024.

Weakness: CWE-863 (Incorrect Authorization), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2025-3838?


## How do I fix CVE-2025-3838?

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

## Is CVE-2025-3838 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3838 and fix it if it is affected.

What it is: CVE-2025-3838 is a medium-severity missing authorization vulnerability in Saviynt OVA based Connect, published on 21 Apr 2025. 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-2025-3838 in the wild and no public exploit code.

Affected product: Saviynt OVA based Connect. 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-2025-3838/ (Markdown: https://insights.sbomify.com/CVE-2025-3838/index.md)
```

## Sources

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

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