CVE Vulnerabilities

CVE-2018-10851

Missing Release of Resource after Effective Lifetime

Published: Nov 29, 2018 | Modified: Oct 09, 2019
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
RedHat/V3
Ubuntu
MEDIUM

PowerDNS Authoritative Server 3.3.0 up to 4.1.4 excluding 4.1.5 and 4.0.6, and PowerDNS Recursor 3.2 up to 4.1.4 excluding 4.1.5 and 4.0.9, are vulnerable to a memory leak while parsing malformed records that can lead to remote denial of service.

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
Authoritative Powerdns 3.3 (including) 4.1.4 (including)
Recursor Powerdns 3.2 (including) 4.1.4 (including)
Pdns Ubuntu bionic *
Pdns Ubuntu cosmic *
Pdns Ubuntu disco *
Pdns Ubuntu eoan *
Pdns Ubuntu groovy *
Pdns Ubuntu hirsute *
Pdns Ubuntu impish *
Pdns Ubuntu kinetic *
Pdns Ubuntu lunar *
Pdns Ubuntu mantic *
Pdns Ubuntu trusty *
Pdns Ubuntu xenial *
Pdns-recursor Ubuntu bionic *
Pdns-recursor Ubuntu cosmic *
Pdns-recursor Ubuntu disco *
Pdns-recursor Ubuntu trusty *
Pdns-recursor Ubuntu upstream *
Pdns-recursor Ubuntu xenial *

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