CVE Vulnerabilities

CVE-2017-14265

Improper Restriction of Operations within the Bounds of a Memory Buffer

Published: Sep 11, 2017 | Modified: Sep 18, 2017
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
3.3 LOW
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Ubuntu

A Stack-based Buffer Overflow was discovered in xtrans_interpolate in internal/dcraw_common.cpp in LibRaw before 0.18.3. It could allow a remote denial of service or code execution attack.

Weakness

The software 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.

Affected Software

Name Vendor Start Version End Version
Libraw Libraw * 0.18.2
Darktable Ubuntu artful *
Darktable Ubuntu cosmic *
Darktable Ubuntu disco *
Darktable Ubuntu eoan *
Darktable Ubuntu groovy *
Darktable Ubuntu hirsute *
Darktable Ubuntu trusty *
Darktable Ubuntu xenial *
Darktable Ubuntu zesty *
Dcraw Ubuntu artful *
Dcraw Ubuntu cosmic *
Dcraw Ubuntu disco *
Dcraw Ubuntu eoan *
Dcraw Ubuntu groovy *
Dcraw Ubuntu hirsute *
Dcraw Ubuntu trusty *
Dcraw Ubuntu xenial *
Dcraw Ubuntu zesty *
Exactimage Ubuntu artful *
Exactimage Ubuntu bionic *
Exactimage Ubuntu cosmic *
Exactimage Ubuntu devel *
Exactimage Ubuntu disco *
Exactimage Ubuntu eoan *
Exactimage Ubuntu focal *
Exactimage Ubuntu groovy *
Exactimage Ubuntu hirsute *
Exactimage Ubuntu impish *
Exactimage Ubuntu jammy *
Exactimage Ubuntu trusty *
Exactimage Ubuntu upstream *
Exactimage Ubuntu xenial *
Exactimage Ubuntu zesty *
Kodi Ubuntu artful *
Kodi Ubuntu cosmic *
Kodi Ubuntu disco *
Kodi Ubuntu eoan *
Kodi Ubuntu groovy *
Kodi Ubuntu hirsute *
Kodi Ubuntu xenial *
Kodi Ubuntu zesty *
Libraw Ubuntu artful *
Libraw Ubuntu esm-infra/xenial *
Libraw Ubuntu trusty *
Libraw Ubuntu upstream *
Libraw Ubuntu xenial *
Libraw Ubuntu zesty *
Rawtherapee Ubuntu artful *
Rawtherapee Ubuntu cosmic *
Rawtherapee Ubuntu disco *
Rawtherapee Ubuntu eoan *
Rawtherapee Ubuntu groovy *
Rawtherapee Ubuntu hirsute *
Rawtherapee Ubuntu trusty *
Rawtherapee Ubuntu xenial *
Rawtherapee Ubuntu zesty *
Ufraw Ubuntu artful *
Ufraw Ubuntu cosmic *
Ufraw Ubuntu disco *
Ufraw Ubuntu trusty *
Ufraw Ubuntu xenial *
Ufraw Ubuntu zesty *
Xbmc Ubuntu trusty *

Extended Description

Certain languages allow direct addressing of memory locations and do not automatically ensure that these locations are valid for the memory buffer that is being referenced. This can cause read or write operations to be performed on memory locations that may be associated with other variables, data structures, or internal program data. As a result, an attacker may be able to execute arbitrary code, alter the intended control flow, read sensitive information, or cause the system to crash.

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

  • For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer.

  • Be wary that a language’s interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

  • Examples include the Safe C String Library (SafeStr) by Messier and Viega [REF-57], and the Strsafe.h library from Microsoft [REF-56]. These libraries provide safer versions of overflow-prone string-handling functions.

  • Run or compile the software using features or extensions that automatically provide a protection mechanism that mitigates or eliminates buffer overflows.

  • For example, certain compilers and extensions provide automatic buffer overflow detection mechanisms that are built into the compiled code. Examples include the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice.

  • Consider adhering to the following rules when allocating and managing an application’s memory:

  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.

  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64].

References