Out-of-Bounds Write in GHSL-2024-228 (CVE-2024-47541)
Summary
Out-of-bounds write in GHSL-2024-228 (CVE-2024-47541). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.24.10 or later.
Original description
The description as published by the source.
GStreamer is a library for constructing graphs of media-handling components. An OOB-write vulnerability has been identified in the gst_ssa_parse_remove_override_codes function of the gstssaparse.c file. This function is responsible for parsing and removing SSA (SubStation Alpha) style override codes, which are enclosed in curly brackets ({}). The issue arises when a closing curly bracket "}" appears before an opening curly bracket "{" in the input string. In this case, memmove() incorrectly duplicates a substring. With each successive loop iteration, the size passed to memmove() becomes progressively larger (strlen(end+1)), leading to a write beyond the allocated memory bounds. This vulnerability is fixed in 1.24.10.
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-2024-47541 has been found in GHSL-2024-228.
Risk of unauthorized operations or information disclosure.
What to do: upgrade GHSL-2024-228 to 1.24.10 or later.
If unsure, ask your IT team or search "GHSL-2024-228 CVE-2024-47541" on the vendor's site.
CVE-2024-47541 (GHSL-2024-228) — CWE-787
Patched: 1.24.10 — 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.
Out-of-bounds write (CWE-787) exists in GHSL-2024-228.
Check the vendor advisory for the affected versions of GHSL-2024-228.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.24.10.
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 'GHSL-2024-228' . 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 'GHSL-2024-228' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
GHSL-2024-228を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade GHSL-2024-228 to 1.24.10ステージング環境で 1.24.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2024-47541 gst-plugins-base Fixed in: 1.24.10-r0
- Debian DEBIAN-CVE-2024-47541 gst-plugins-base1.0 Fixed in: 1.18.4-2+deb11u3
- Ubuntu UBUNTU-CVE-2024-47541 gst-plugins-base0.10
References
- advisory github.com
- advisory nvd.nist.gov
- advisory securitylab.github.com
- patch gitlab.freedesktop.org
- web gstreamer.freedesktop.org
- web lists.debian.org