# CVE-2024-8969: The SYSCOM Group OMFLOW - Exposure of Sensitive Data

> Authenticated attackers can retrieve password hashes for all users and administrators in The SYSCOM Group OMFLOW.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-8vqf-p95r-7frg

## What is CVE-2024-8969?

CVE-2024-8969 is a medium-severity vulnerability in The SYSCOM Group OMFLOW, published on 18 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OMFLOW from The SYSCOM Group has a vulnerability involving the exposure of sensitive data. This allows remote attackers who have logged into the system to obtain password hashes of all users and administrators.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2024-8969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8969 is a medium-severity vulnerability in The SYSCOM Group OMFLOW, published on 18 Sep 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-8969 in the wild and no public exploit code.

Affected product: The SYSCOM Group OMFLOW. 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-8969/ (Markdown: https://insights.sbomify.com/CVE-2024-8969/index.md)
```

## Sources

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

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