dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2024-44866

MEDIUM · 6.8 CVSS v3.1 Published 2025-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability exists in the GuitarPro1::read function of MuseScore Studio v4.3.2 when parsing GuitarPro files. Attackers can exploit this by crafting a malicious GuitarPro file with oversized data that overwrites adjacent memory during parsing, enabling arbitrary code execution or causing a denial of service.

MitigationUntil an official patch is available, avoid opening GuitarPro files from untrusted sources. Consider implementing additional input validation and bounds checking in the GuitarPro1::read function to prevent buffer overflows during file parsing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if MuseScore Studio is installed
    Check for MuseScore Studio installation by looking for the application in common locations: Windows (C:\Program Files\MuseScore\ or C:\Program Files (x86)\MuseScore\), macOS (/Applications/MuseScore.app), or Linux (check package manager with 'dpkg -l | grep musescore' or 'rpm -qa | grep musescore'). Also check if the executable 'MuseScore4.exe' or 'mscore' exists on the system.
    Affected if MuseScore Studio v4.3.2 is installed on the system
  2. Confirm the installed version of MuseScore Studio
    Run the application and navigate to Help > About MuseScore, or use command line: 'MuseScore4.exe --version' or 'mscore --version' on Linux. Alternatively, check the executable file properties for version information.
    Affected if The installed version is 4.3.2 or if the version cannot be determined but the software is present and parses GuitarPro files
  3. Verify GuitarPro file import capability is present
    Attempt to open a GuitarPro file (.gtp, .gp3, .gp4, .gp5, .gpx) in MuseScore Studio through File > Open, or check if GuitarPro appears as a supported format in File > Import > Supported Formats. On Linux, also check ~/.local/share/MuseScore/ or /usr/share/MuseScore for any GuitarPro-related libraries or plugins.
    Affected if GuitarPro file format support is available in the installation and users can import such files
  4. Check for recent GuitarPro file processing activity
    Review the application log files (typically found in the application data directory such as %APPDATA%\MuseScore\MuseScore4\logs\ on Windows or ~/.local/share/MuseScore/MuseScore4/logs/ on Linux/macOS) for entries mentioning 'GuitarPro', 'GuitarPro1', or 'read' function calls. Also check for any crash dumps or error logs related to .gtp/.gp files.
    Affected if GuitarPro files have been recently opened or there are crash logs indicating parsing of GuitarPro files occurred

A user is affected if MuseScore Studio v4.3.2 is installed and the GuitarPro file import feature is available, allowing malicious oversized GuitarPro files to trigger the buffer overflow during parsing.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until an official patch is available, avoid opening GuitarPro files from untrusted sources. Consider implementing additional input validation and bounds checking in the GuitarPro1::read function to prevent buffer overflows during file parsing.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-44866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-44866 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data