Vulnerability in MediaMonkey (CVE-2019-25571)
Summary
Vulnerability in MediaMonkey (CVE-2019-25571). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
MediaMonkey 4.1.23 contains a denial of service vulnerability that allows local attackers to crash the application by opening a specially crafted MP3 file containing an excessively long URL string. Attackers can create a malicious MP3 file with a buffer containing 4000 bytes of data appended to a URL, which causes the application to crash when the file is opened through the File > Open URL dialog.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2019-25571 has been found in MediaMonkey.
Risk of unauthorized operations or information disclosure. CVSS score: 6.2/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "MediaMonkey CVE-2019-25571" on the vendor's site.
CVE-2019-25571 (MediaMonkey) — CWE-226 / CVSS v3 6.2
Attack vector: local / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-226) exists in MediaMonkey.
Check the vendor advisory for the affected versions of MediaMonkey.
Severity: Medium (CVSS 6.2/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'MediaMonkey' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'MediaMonkey' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
MediaMonkeyを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory disclosure@vulncheck.com
- exploit disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com