Vulnerability in gpac (DEBIAN-CVE-2021-21848)

Summary

Vulnerability in gpac (DEBIAN-CVE-2021-21848). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.1+dfsg1-4+deb11u1 or later.

Original description

The description as published by the source.

An exploitable integer overflow vulnerability exists within the MPEG-4 decoding functionality of the GPAC Project on Advanced Content library v1.0.1. The library will actually reuse the parser for atoms with the “stsz” FOURCC code when parsing atoms that use the “stz2” FOURCC code and can cause an integer overflow due to unchecked arithmetic resulting in a heap-based buffer overflow that causes memory corruption. An attacker can convince a user to open a video to trigger this vulnerability.

Source: OSV.dev (Open Source Vulnerabilities) OSV

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 DEBIAN-CVE-2021-21848 has been found in gpac.
Successful exploitation can lead to full system takeover.
What to do: upgrade gpac to 1.0.1+dfsg1-4+deb11u1 or later.
If unsure, ask your IT team or search "gpac DEBIAN-CVE-2021-21848" on the vendor's site.

DEBIAN-CVE-2021-21848 (gpac)
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.0.1+dfsg1-4+deb11u1 — 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.

❓ What is the problem

A vulnerability (unclassified) exists in gpac.

📍 Affected scope

Check the vendor advisory for the affected versions of gpac.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.0.1+dfsg1-4+deb11u1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gpac' . 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

1
Identify exposure identify
```
grep -r 'gpac' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gpac を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade gpac to 1.0.1+dfsg1-4+deb11u1
```
ステージング環境で 1.0.1+dfsg1-4+deb11u1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 gpac

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.1+dfsg1-4+deb11u1"}]}]

References

advisory security-tracker.debian.org