CVE-2024-2364 json
Musicshelf Backup androidmanifest.xml backup
published 2y ago modified 4mo ago also EUVD-2024-27317
- cvss
- 1.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
A vulnerability classified as problematic has been found in Musicshelf 1.0/1.1 on Android. Affected is an unknown function of the file androidmanifest.xml of the component Backup Handler. The manipulation leads to exposure of backup file to an unauthorized control sphere. It is possible to launch the attack on the physical device. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-256320.
Is CVE-2024-2364 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/ctflearner/Android_Findings/blob/main/Musicshelf/Musicshelf_Manifest_issue.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 1.8 | CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.0 | 1.8 | CVSS:3.0/AV:P/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| CNA | 2.0 | 1.4 | AV:L/AC:L/Au:M/C:P/I:N/A:N |
| NVD | 3.1 | 4.6 | CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- n/a Musicshelf
- musicshelf musicshelf
Classification
References
-
github.com
/ctflearner/Android_Findings/blob/main/Musicshelf/Musicshelf_Manifest_issue.md
exploit
-
vuldb.com
/?id.256320
vdb-entry, permissions-required
-
vuldb.com
/?ctiid.256320
signature, permissions-required
Sources
- CVE List CVE-2024-2364
- NVD CVE-2024-2364
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.