Out-of-Bounds Read in java (CVE-2024-47775)
Summary
Vulnerability in java (CVE-2024-47775). 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-read vulnerability has been found in the parse_ds64 function within gstwavparse.c. The parse_ds64 function does not check that the buffer buf contains sufficient data before attempting to read from it, doing multiple GST_READ_UINT32_LE operations without performing boundary checks. This can lead to an OOB-read when buf is smaller than expected. This vulnerability allows reading beyond the bounds of the data buffer, potentially leading to a crash (denial of service) or the leak of sensitive data. 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-47775 has been found in java.
Risk of unauthorized operations or information disclosure.
What to do: upgrade java to 1.24.10 or later.
If unsure, ask your IT team or search "java CVE-2024-47775" on the vendor's site.
CVE-2024-47775 (java) — CWE-125
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 read (CWE-125) exists in java.
Check the vendor advisory for the affected versions of java.
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 'java' . 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 'java' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
javaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade java to 1.24.10ステージング環境で 1.24.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2024-47775 gst-plugins-good1.0 Fixed in: 1.18.4-2+deb11u3
- Ubuntu UBUNTU-CVE-2024-47775 gst-plugins-good0.10
References
- advisory securitylab.github.com
- advisory github.com
- patch gitlab.freedesktop.org
- web gstreamer.freedesktop.org
- web lists.debian.org
- web nvd.nist.gov