disclosure of a heap buffer overflow vulnerability
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 8/100
Research direction
This is a private-disclosure report with no technical detail: the payload names no file, line, input or crash signature, so nothing can be reproduced from the issue text alone. A maintainer would first have to reply to [email protected] for the reproducer, then work from the decoder entry points in the single minimp3.h header. Done means a crafted MP3 no longer overflows the heap buffer and the fix is confirmed against the reporter's sample; it is coordination work, not a first-timer task.
Written by the indexing model from the issue text.
Description
Hi maintainer,
I'm a security researcher and I've identified a heap buffer overflow vulnerability within the latest version of the minimp3 library.
This vulnerability can be triggered by processing a maliciously crafted MP3 file, which may lead to application crash or other potential security impacts.
I adhere to responsible disclosure practices. Please reach out to me via my email: [email protected] if you would like to receive full technical details, reproduction steps, or other related information privately.
I intend to apply for a CVE ID for this vulnerability after proper notification. Thank you for your attention to this security issue.
Best regards.
Lidi Jie
- Dominant language
- C
- Stars
- 2k
- Forks
- 271
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lieff/minimp3
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
[Bug]signed left-shift overflow in mp3dec_skip_id3v1 when parsing the APEv2 tag-size field (CWE-190)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Integer overflow in Xing/Info VBR header parsing leads to ~10TB allocation (DoS)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 Half a day Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Similar issues
-
vim.filetype.match() prefixes a URL buffer name with the cwd before passing it to filetype functionsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
stream_curl: retry_count never resets after a successful reconnect, so long sequential streams die after 5 dropsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
mpv-player/mpv#18728 ·
Maintainers usually reply within 1 day
-
followup Prio 📌
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cyrusimap/cyrus-imapd#6640 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
Maintainers usually reply within 1 day