CVE Vulnerabilities

CVE-2017-12962

Missing Release of Resource after Effective Lifetime

Published: Aug 18, 2017 | Modified: Oct 03, 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
LOW

There are memory leaks in LibSass 3.4.5 triggered by deeply nested code, such as code with a long sequence of open parenthesis characters, leading to a remote denial of service attack.

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
Libsass Libsass 3.4.5 (including) 3.4.5 (including)
Libsass Ubuntu artful *
Libsass Ubuntu bionic *
Libsass Ubuntu cosmic *
Libsass Ubuntu devel *
Libsass Ubuntu disco *
Libsass Ubuntu eoan *
Libsass Ubuntu esm-apps/bionic *
Libsass Ubuntu esm-apps/focal *
Libsass Ubuntu esm-apps/jammy *
Libsass Ubuntu esm-apps/noble *
Libsass Ubuntu esm-apps/xenial *
Libsass Ubuntu focal *
Libsass Ubuntu groovy *
Libsass Ubuntu hirsute *
Libsass Ubuntu impish *
Libsass Ubuntu jammy *
Libsass Ubuntu kinetic *
Libsass Ubuntu lunar *
Libsass Ubuntu mantic *
Libsass Ubuntu noble *
Libsass Ubuntu upstream *
Libsass Ubuntu xenial *
Libsass 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