# CVE-2024-44866: Memory corruption in n/a

> Attackers can execute arbitrary code or cause denial of service by tricking users into opening a crafted GuitarPro file in MuseScore Studio.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Mar 2025
- **Updated:** 19 Mar 2025
- **Also known as:** DEBIAN-CVE-2024-44866, GHSA-xw57-qhqx-v67p, UBUNTU-CVE-2024-44866

## What is CVE-2024-44866?

CVE-2024-44866 is a medium-severity memory corruption vulnerability in n/a, published on 17 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A buffer overflow in the GuitarPro1::read function of MuseScore Studio v4.3.2 allows attackers to to execute arbitrary code or cause a Denial of Service (DoS) via opening a crafted GuitarPro file.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

Upgrade to a fixed version.

## Is CVE-2024-44866 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44866 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-44866 is a medium-severity memory corruption vulnerability in n/a, published on 17 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-44866 exists.

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

## Sources

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

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