# CVE-2024-25654: Information disclosure in n/a

> Local attackers can read log files to steal credentials and decrypt sensitive database data in AVSystem UMP.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 18 Mar 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-3phv-44jf-4v33

## What is CVE-2024-25654?

CVE-2024-25654 is a medium-severity vulnerability in n/a, published on 18 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insecure permissions for log files of AVSystem Unified Management Platform (UMP) 23.07.0.16567~LTS allow members (with local access to the UMP application server) to access credentials to authenticate to all services, and to decrypt sensitive data stored in the database.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-25654?

It affects 1 product.


Products: Avsystem Unified Management Platform.

## How do I fix CVE-2024-25654?

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

## Is CVE-2024-25654 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25654 and fix it if it is affected.

What it is: CVE-2024-25654 is a medium-severity vulnerability in n/a, published on 18 Mar 2024. 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-2024-25654 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-2024-25654/ (Markdown: https://insights.sbomify.com/CVE-2024-25654/index.md)
```

## Sources

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

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