FFmpeg up to 2.0 Block Lenghts libavcodec/jpeg2000dec.c jpeg2000_decode_packet Local Privilege Escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in FFmpeg up to 2.0. This affects the function jpeg2000_decode_packet of the file libavcodec/jpeg2000dec.c of the component Block Lenghts Handler. Performing a manipulation results in an unknown weakness.
There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic has been found in FFmpeg up to 2.0 (Multimedia Processing Software). This affects the function jpeg2000_decode_packet of the file libavcodec/jpeg2000dec.c of the component Block Lenghts Handler. The impact remains unknown.
The weakness was presented 10/09/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as jpeg2000: Check block length as confirmed git commit (GIT Repository). It is possible to read the advisory at git.videolan.org. The public release was coordinated in cooperation with the project team. Technical details of the vulnerability are known, but there is no available exploit.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.libav.org. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (98361†). See VDB-10682, VDB-10681 and VDB-10679 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- FFmpeg 2.0
- Libav 9.9
Product
Type
Name
Version
License
Website
- Product: https://ffmpeg.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Local Privilege EscalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.libav.org
Timeline
10/09/2013 🔍10/09/2013 🔍
10/15/2013 🔍
05/13/2018 🔍
Sources
Product: ffmpeg.orgAdvisory: jpeg2000: Check block length
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-10683
OSVDB: 98361
See also: 🔍
Entry
Created: 10/15/2013 12:24Updated: 05/13/2018 10:23
Changes: 10/15/2013 12:24 (48), 05/13/2018 10:23 (1)
Complete: 🔍
Committer: olku
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.