CVE-2018-15209
Public on
Last Modified:
Description
The CVE Program describes this issue as:
ChopUpSingleUncompressedStrip in tif_dirread.c in LibTIFF 4.0.9 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted TIFF file, as demonstrated by tiff2pdf.
Statement
Red Hat has determined that this vulnerability has a moderate severity due to a series of factors. Firstly, the attack vector necessary to successfully exploit this flaw is local, given that the attacker must rely on user interaction (by tricking or fooling them into opening a maliciously-crafted TIFF file). Secondly, the CIA impact of this vulnerability should be assumed to be Low for all three vectors, due to to the fact that a successful crash would only impact the LibTIFF application itself, the application does not inherently have access to nor handle sensitive or confidential information, and since it causes a DoS due to heap-based buffer overflow there is little indication that this will modify or alter data.
This issue did not affect the versions of libtiff as shipped with Red Hat Enterprise Linux 5, 6, and 7.
Additional information
- Bugzilla 1614051: libtiff: Heap-based buffer overflow in ChopUpSingleUncompressedStrip in tif_dirread.c
- CWE-122: Heap-based Buffer Overflow
- FAQ: Frequently asked questions about CVE-2018-15209
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
Red Hat | NVD | |
---|---|---|
CVSS v3 Base Score | 5.3 | 8.8 |
Attack Vector | Local | Network |
Attack Complexity | Low | Low |
Privileges Required | None | None |
User Interaction | Required | Required |
Scope | Unchanged | Unchanged |
Confidentiality Impact | Low | High |
Integrity Impact | Low | High |
Availability Impact | Low | High |
CVSS v3 Vector
Red Hat: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
NVD: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.