Path Traversal in cherrymusic (CVE-2015-8309)
Summary
Path traversal in cherrymusic (CVE-2015-8309). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 62dec34a1ea0741400dd6b6c660d303dcd651e86, 0.36.0 or later.
Original description
The description as published by the source.
Directory traversal vulnerability in Cherry Music before 0.36.0 allows remote authenticated users to read arbitrary files via the "value" parameter to "download."
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2015-8309 has been found in cherrymusic.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade cherrymusic to 62dec34a1ea0741400dd6b6c660d303dcd651e86, 0.36.0 or later.
If unsure, ask your IT team or search "cherrymusic CVE-2015-8309" on the vendor's site.
CVE-2015-8309 (cherrymusic) — CWE-22 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 62dec34a1ea0741400dd6b6c660d303dcd651e86, 0.36.0 — apply immediately
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.
Path traversal (CWE-22) exists in cherrymusic.
Check the vendor advisory for the affected versions of cherrymusic.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 62dec34a1ea0741400dd6b6c660d303dcd651e86, 0.36.0.
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 'cherrymusic' . 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 'cherrymusic' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
cherrymusicを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade cherrymusic to 62dec34a1ea0741400dd6b6c660d303dcd651e86, 0.36.0ステージング環境で 62dec34a1ea0741400dd6b6c660d303dcd651e86, 0.36.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- report github.com
- web fomori.org
- web securityfocus.com
- web exploit-db.com