CVE-2016-10191: Heap-based buffer overflow in libavformat/rtmppkt.c in FFmpeg before 2.8.10, 3.0.x before 3.0.5, 3.1.x before 3.1.6, and 3.2.x before 3.2.2…
Noroxi assessment
Priority: Plan (action score 41/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.4% (FIRST EPSS); higher than 94.5% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: ffmpeg (Alpine:v3.3) 2.8.11-r0; ffmpeg (Alpine:v3.4) 3.0.7-r0; ffmpeg (Debian:12) 7:3.2.2-1.
Add it to your regular patch cycle. Upgrade to ffmpeg (Alpine:v3.3) 2.8.11-r0; ffmpeg (Alpine:v3.4) 3.0.7-r0; ffmpeg (Debian:12) 7:3.2.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Heap-based buffer overflow in libavformat/rtmppkt.c in FFmpeg before 2.8.10, 3.0.x before 3.0.5, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 allows remote attackers to execute arbitrary code by leveraging failure to check for RTMP packet size mismatches.
- Published
- Feb 9, 2017
- Updated
- Jun 16, 2026
- EPSS
- 7.4% · 94th percentile
- CWE
- CWE-119
Report tools
Action score
41
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ffmpeg | ffmpeg | cpe:2.3:a:ffmpeg:ffmpeg |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ffmpeg ffmpegup to 2.8.9 inclusive
- ffmpeg ffmpeg3.0
- ffmpeg ffmpeg3.0.1
- ffmpeg ffmpeg3.0.2
- ffmpeg ffmpeg3.0.3
- ffmpeg ffmpeg3.0.4
- ffmpeg ffmpeg3.1
- ffmpeg ffmpeg3.1.1
+6 more rows
- ffmpeg ffmpeg3.1.2
- ffmpeg ffmpeg3.1.3
- ffmpeg ffmpeg3.1.4
- ffmpeg ffmpeg3.1.5
- ffmpeg ffmpeg3.2
- ffmpeg ffmpeg3.2.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.3 | ffmpeg | before 2.8.11-r0 | 2.8.11-r0 |
| Alpine:v3.4 | ffmpeg | before 3.0.7-r0 | 3.0.7-r0 |
| Debian:12 | ffmpeg | before 7:3.2.2-1 | 7:3.2.2-1 |
| Debian:8 | libav | before 6:11.12-1~deb8u2 | 6:11.12-1~deb8u2 |
| openSUSE:Tumbleweed | ffmpeg-4 | before 4.4-5.2 | 4.4-5.2 |
| SUSE:Package Hub 12 SP1 | ffmpeg2 | before 2.8.11-12.1 | 2.8.11-12.1 |
| SUSE:Package Hub 12 SP2 | ffmpeg | before 3.1.8-8.1 | 3.1.8-8.1 |
Same product
ffmpeg: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-4637FFmpeg 0.5 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via unknown vectors that…45Plan
- CVE-2016-10190Heap-based buffer overflow in libavformat/http.c in FFmpeg before 2.8.10, 3.0.x before 3.0.5, 3.1.x before 3.1.6, and 3.2.x before 3.2.2…42Plan
- CVE-2009-4634Multiple integer underflows in FFmpeg 0.5 allow remote attackers to cause a denial of service and possibly execute arbitrary code via a…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-6164Jan 23, 2017 · Integer overflow in the mov_build_index function in libavformat/mov.c in FFmpeg before 2.8.8, 3.0.x before 3.0.3 and 3.1.x before 3.1.1…40Plan
- ← EarlierCVE-2016-6920Jan 23, 2017 · Heap-based buffer overflow in the decode_block function in libavcodec/exr.c in FFmpeg before 3.1.3 allows remote attackers to cause a…31Monitor
- Later →CVE-2016-10192Feb 9, 2017 · Heap-based buffer overflow in ffserver.c in FFmpeg before 2.8.10, 3.0.x before 3.0.5, 3.1.x before 3.1.6, and 3.2.x before 3.2.2 allows…41Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:ffmpeg | 2.8.11-r0 · Alpine:v3.3 | Package registry (OSV) |
| debian:ffmpeg | 7:3.2.2-1 · Debian:12 | Package registry (OSV) |
| debian:libav | 6:11.12-1~deb8u2 · Debian:8 | Package registry (OSV) |
| opensuse:ffmpeg-4 | 4.4-5.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:ffmpeg | 3.1.8-8.1 · SUSE:Package Hub 12 SP2 | Package registry (OSV) |
| suse:ffmpeg2 | 2.8.11-12.1 · SUSE:Package Hub 12 SP1 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2022-12-12 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+2132 d
- TodayNov 15, 2026+3566 d
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.