FFmpeg 1.2.1 TPsot libavcodec/jpeg2000dec.c get_sot privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in FFmpeg 1.2.1. This affects the function get_sot of the file libavcodec/jpeg2000dec.c of the component TPsot Handler. Performing a manipulation results in privileges management.
There is not any exploit available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical has been found in FFmpeg 1.2.1 (Multimedia Processing Software). This affects the function get_sot of the file libavcodec/jpeg2000dec.c of the component TPsot Handler. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, and integrity.
The issue has been introduced in 05/10/2013. The weakness was released 05/22/2013 by Mateusz Jurczyk and Gynvael Coldwind with Google Security Team as jpeg2000dec: check TPsot as confirmed git commit (GIT Repository). It is possible to read the advisory at git.videolan.org. The public release was coordinated with the project team. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
The vulnerability was handled as a non-public zero-day exploit for at least 12 days. During that time the estimated underground price was around $0-$5k.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.videolan.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 (94268†). Entries connected to this vulnerability are available at VDB-9175, VDB-9174, VDB-9173 and VDB-9172. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 6.5VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
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: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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.videolan.org
Timeline
05/10/2013 🔍05/22/2013 🔍
05/22/2013 🔍
06/17/2013 🔍
04/15/2019 🔍
Sources
Product: ffmpeg.orgAdvisory: jpeg2000dec: check TPsot
Researcher: Mateusz Jurczyk, Gynvael Coldwind
Organization: Google Security Team
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-9171
OSVDB: 94268
See also: 🔍
Entry
Created: 06/17/2013 11:06Updated: 04/15/2019 14:36
Changes: 06/17/2013 11:06 (51), 04/15/2019 14:36 (2)
Complete: 🔍
Cache ID: 216:018: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.