Pillow up to 3.1.1 JPEG2000 File j2k_encode_entry memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Pillow up to 3.1.1. This vulnerability affects the function j2k_encode_entry of the component JPEG2000 File Handler. Such manipulation leads to memory corruption.
This vulnerability is uniquely identified as CVE-2016-3076. Local access is required to approach this attack. No exploit exists.
Details
A vulnerability, which was classified as problematic, has been found in Pillow up to 3.1.1. Affected by this issue is the function j2k_encode_entry of the component JPEG2000 File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability. CVE summarizes:
Heap-based buffer overflow in the j2k_encode_entry function in Pillow 2.5.0 through 3.1.1 allows remote attackers to cause a denial of service (memory corruption) via a crafted Jpeg2000 file.
The bug was discovered 03/29/2016. The weakness was disclosed 04/24/2017 with Atlassian (Website). The advisory is shared for download at pillow.readthedocs.io. This vulnerability is handled as CVE-2016-3076 since 03/10/2016. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 391 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 98042†). Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 867773
OpenVAS Name: Fedora Update for python-pillow FEDORA-2016-6
OpenVAS File: 🔍
OpenVAS Family: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/10/2016 🔍03/29/2016 🔍
03/29/2017 🔍
04/24/2017 🔍
04/24/2017 🔍
04/25/2017 🔍
12/21/2020 🔍
Sources
Advisory: pillow.readthedocs.ioResearcher: Alyssa Besseling at Atlassian.
Organization: Atlassian
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-3076 (🔍)
GCVE (CVE): GCVE-0-2016-3076
GCVE (VulDB): GCVE-100-100532
SecurityFocus: 98042 - Pillow CVE-2016-3076 Heap Buffer Overflow Vulnerability
OSVDB: - CVE-2016-3076 - Pillow - Memory Corruption Issue
Entry
Created: 04/25/2017 08:53Updated: 12/21/2020 13:33
Changes: 04/25/2017 08:53 (63), 09/20/2020 16:37 (6), 12/21/2020 13:33 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.