CVE Vulnerabilities

CVE-2017-14495

Missing Release of Resource after Effective Lifetime

Published: Oct 03, 2017 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
7.8 IMPORTANT
AV:N/AC:L/Au:N/C:N/I:N/A:C
RedHat/V3
7.5 IMPORTANT
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

Memory leak in dnsmasq before 2.78, when the –add-mac, –add-cpe-id or –add-subnet option is specified, allows remote attackers to cause a denial of service (memory consumption) via vectors involving DNS response creation.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

Name Vendor Start Version End Version
Ubuntu_linux Canonical 14.04 (including) 14.04 (including)
Ubuntu_linux Canonical 16.04 (including) 16.04 (including)
Ubuntu_linux Canonical 17.04 (including) 17.04 (including)
Debian_linux Debian 7.0 (including) 7.0 (including)
Debian_linux Debian 7.1 (including) 7.1 (including)
Debian_linux Debian 9.0 (including) 9.0 (including)
Leap Novell 42.2 (including) 42.2 (including)
Leap Novell 42.3 (including) 42.3 (including)
Enterprise_linux_desktop Redhat 7.0 (including) 7.0 (including)
Enterprise_linux_server Redhat 7.0 (including) 7.0 (including)
Enterprise_linux_workstation Redhat 7.0 (including) 7.0 (including)
Red Hat Enterprise Linux 7 RedHat dnsmasq-0:2.76-2.el7_4.2 *
Dnsmasq Ubuntu trusty *
Dnsmasq Ubuntu xenial *
Dnsmasq Ubuntu zesty *

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, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References