# CVE-2024-4425: Storing credentials in plaintext in CemiPark

> Attackers with device access can retrieve plaintext integration credentials, exposing sensitive system passwords.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **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:** 9 May 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-vcx5-gghv-x2hh

## What is CVE-2024-4425?

CVE-2024-4425 is a medium-severity vulnerability in CemiPark, published on 9 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The access control in CemiPark software stores integration (e.g. FTP or SIP) credentials in plain-text. An attacker who gained unauthorized access to the device can retrieve clear text passwords used by the system.This issue affects CemiPark software: 4.5, 4.7, 5.03 and potentially others. The vendor refused to provide the specific range of affected products.

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2024-4425 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4425 is a medium-severity vulnerability in CemiPark, published on 9 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4425 in the wild and no public exploit code.

Affected product: CemiPark. 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-4425/ (Markdown: https://insights.sbomify.com/CVE-2024-4425/index.md)
```

## Sources

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

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