# CVE-2019-25089: Morgawr Muon handler.clj random values

> Insufficiently random values in the handler allow remote attackers to bypass security controls, requiring an upgrade to the latest version.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/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:** 27 Dec 2022
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9rj9-4qhw-j56j

## What is CVE-2019-25089?

CVE-2019-25089 is a low-severity vulnerability in Morgawr Muon, published on 27 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in Morgawr Muon 0.1.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file src/muon/handler.clj. The manipulation leads to insufficiently random values. The attack can be launched remotely. Upgrading to version 0.2.0-indev is able to address this issue. The name of the patch is c09ed972c020f759110c707b06ca2644f0bacd7f. It is recommended to upgrade the affected component. The identifier VDB-216877 was assigned to this vulnerability.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2019-25089?

It affects 1 product.


Products: Muon Project Muon.

## How do I fix CVE-2019-25089?

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

## Is CVE-2019-25089 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25089 and fix it if it is affected.

What it is: CVE-2019-25089 is a low-severity vulnerability in Morgawr Muon, published on 27 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25089 in the wild and no public exploit code.

Affected product: Morgawr Muon. 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-2019-25089/ (Markdown: https://insights.sbomify.com/CVE-2019-25089/index.md)
```

## Sources

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

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