Your message dated Tue, 22 Apr 2025 20:34:43 +0000
with message-id <[email protected]>
and subject line Bug#1070860: fixed in musescore2 2.3.2+dfsg4-16
has caused the Debian Bug report #1070860,
regarding musescore3: CVE-2023-44428 CVE-2024-44866
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1070860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070860
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: musescore3
X-Debbugs-CC: [email protected]
Severity: important
Tags: security

Hi,

The following vulnerability was published for musescore3.

CVE-2023-44428[0]:
| MuseScore CAP File Parsing Heap-based Buffer Overflow Remote Code
| Execution Vulnerability. This vulnerability allows remote attackers
| to execute arbitrary code on affected installations of MuseScore.
| User interaction is required to exploit this vulnerability in that
| the target must visit a malicious page or open a malicious file.
| The specific flaw exists within the parsing of CAP files. The issue
| results from the lack of proper validation of the length of user-
| supplied data prior to copying it to a heap-based buffer. An
| attacker can leverage this vulnerability to execute code in the
| context of the current process. Was ZDI-CAN-20769.

Unfortunatetly details are sparse, the only reference is
https://www.zerodayinitiative.com/advisories/ZDI-23-1526/


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-44428
    https://www.cve.org/CVERecord?id=CVE-2023-44428

Please adjust the affected versions in the BTS as needed.

--- End Message ---
--- Begin Message ---
Source: musescore2
Source-Version: 2.3.2+dfsg4-16
Done: Thorsten Glaser <[email protected]>

We believe that the bug you reported is fixed in the latest version of
musescore2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Glaser <[email protected]> (supplier of updated musescore2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

Format: 1.8
Date: Tue, 22 Apr 2025 02:52:14 +0000
Source: musescore2
Architecture: source
Version: 2.3.2+dfsg4-16
Distribution: unstable
Urgency: high
Maintainer: Thorsten Glaser <[email protected]>
Changed-By: Thorsten Glaser <[email protected]>
Closes: 1070860
Changes:
 musescore2 (2.3.2+dfsg4-16) unstable; urgency=high
 .
   * Update description:
     - the musescore.org software has been renamed upstream to
       Mu͒seScore Studio and the musescore.com website to
       Mu͒seScore Catalogue and the mobile äpps to
       Mu͒seScore Sheet Music for Android and iOS
       ⇒ follow that
     - cease naming commercial competitors it’s supposedly better than
     - update situation description for major version 2 vs. 3
     - document no v4 package is planned due to the freeness reduction
     - plan to package “Mu͒seScore 3 Evolution” (community-maintained
       3.7 fork) as musescore-snapshot (as it has no releases anyway)
     - document Muse Group company takeover, remove mentions of old one
     - reduce delta between v2/v3 descriptions
   * Backport fixes:
     - Help→MusicXML: link correct licence (from mu͒ Evolution)
     - Fix for CVE-2024-44866 (from mu͒4); (Closes: #1070860)
   * Add README.Debian to explicitly express that this should not be
     exposed to untrusted input files without confinement (cf. #1070860)
   * Work around unexpected colourised messages from cmake’s tester
   * Try to blindly fix CVE-2023-44428: (addresses #1070860 as well)
     - improve Capella import robustness
     - arm Q_ASSERT{,_X} macros to exercise the tests and log failures and,
       if MSCORE_ASSERT_ABORT is set, make assertion failure abort()
   * Improve stderr log formatting and omit debug level, except -d is used
   * Bump Policy, transition to libfreetype-dev
   * Update lintian overrides for sid
Checksums-Sha1:
 5f78501b53a85bcbe9a39d14c6ccf6a03b61810c 2702 musescore2_2.3.2+dfsg4-16.dsc
 8c4d84c6c519cd12e3932507dc4c61987616d3da 139676 
musescore2_2.3.2+dfsg4-16.debian.tar.xz
Checksums-Sha256:
 34bb5f15e719b13702a188bb2378c902d62476c2cdf82bd8832e818a41af2224 2702 
musescore2_2.3.2+dfsg4-16.dsc
 101fd910eeb909dd1c9577a7b256e9939cafc5cbe07e6541f470d831cdfca64b 139676 
musescore2_2.3.2+dfsg4-16.debian.tar.xz
Files:
 f55ff62eb7a0f99a5c71216088924d25 2702 sound optional 
musescore2_2.3.2+dfsg4-16.dsc
 88672cd927fbbb6f746c6ea55f937a65 139676 sound optional 
musescore2_2.3.2+dfsg4-16.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (MirBSD)

iQIcBAEBCQAGBQJoB/TAAAoJEHa1NLLpkAfgkzwQALMpRI1v7PgAaT3PLjZcclKf
2zPi4cbfVbRrpRxdAv7Cj32dNUaktR8CughyLPUIEvC65cPX+Y7hdMNaF/bL7TYC
sE9nEVIk8+WT+F989/lrmXCVq0AlsPRqIJ/PtTb1N6JtXJ010EBlZgIOydkS7Jh7
dRU+dDIYzt691MjIvoDXixJ4Nr9JBHF0M8Va3U6COzHpLlJAqF+Ab05O3TjRJHwk
aipfpbKrGHggAevfP4uVOIVFuhjFyf3Z0XjwzJAlFC9uypDct+EQT95yf/R+e+CY
R5yggwok/ak6Nat6XRk3xqezxAY4VXkekq84mmo/GhNsWVOaw1hfhPEn8tUsFYWo
2H7dyiX0x9C2hLQFL+bAhdcUlo0kIteeKZyC/nyYDDOF8s/7SNH3SDlg12iMY0rH
RXAMZSErpx0dYEiFaAbXw1yS0ttID/iuC8QEg4Hf1nizpRojBpPsKeUyf7TCbUoU
rKarxZRHWE6nhvLhHu3fPTajzQaUB6rnz7Dk/2XGL25XMhVN8hDqXg4Ht7/pzB1U
1uDAX0qgeaB6OYiQWTE/LlzwzHdMxE09xLMaRcTL1HZIcvtkALyZOx4nYirzMVQc
OuqY9GFJ7UJ3ynIuYO9bS6bbEqUzHuf4HaOHI3dtxG83zedfWUKlYPAGggLrnv8Z
ljGmb1p0ckr+o06di1xE
=4m99
-----END PGP SIGNATURE-----

Attachment: pgpWY0zPKpxtW.pgp
Description: PGP signature


--- End Message ---

Reply via email to