# CVE-2024-45785: Information disclosure in MUSASI

> An attacker can retrieve other users' credentials and sensitive information due to improper client-side authentication in MUSASI.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-pcrm-w585-fvg9

## What is CVE-2024-45785?

CVE-2024-45785 is a high-severity vulnerability in NEUMANN CO.LTD. MUSASI, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MUSASI version 3 contains an issue with use of client-side authentication. If this vulnerability is exploited, other users' credential and sensitive information may be retrieved.

Weakness: CWE-603 (Use of Client-Side Authentication)

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

It affects 1 product.


Products: Neumann Musasi.

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

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

## Is CVE-2024-45785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45785 is a high-severity vulnerability in NEUMANN CO.LTD. MUSASI, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45785 in the wild and no public exploit code.

Affected product: NEUMANN CO.LTD. MUSASI. 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-45785/ (Markdown: https://insights.sbomify.com/CVE-2024-45785/index.md)
```

## Sources

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

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