CVE Vulnerabilities


Missing Release of Resource after Effective Lifetime

Published: Oct 14, 2015 | Modified: Sep 08, 2021
CVSS 3.x
CVSS 2.x

The addForegroundSprite function in Adobe Reader and Acrobat 10.x before 10.1.16 and 11.x before 11.0.13, Acrobat and Acrobat Reader DC Classic before 2015.006.30094, and Acrobat and Acrobat Reader DC Continuous before 2015.009.20069 on Windows and OS X allows attackers to obtain sensitive information from process memory via invalid arguments, a different vulnerability than CVE-2015-6697, CVE-2015-6700, CVE-2015-6701, CVE-2015-6702, CVE-2015-6703, and CVE-2015-6704.


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
Acrobat Adobe 10.0 (including) 10.1.15 (including)
Acrobat Adobe 11.0.0 (including) 11.0.12 (including)
Acrobat_dc Adobe 15.006.30060 (including) 15.006.30094 (excluding)
Acrobat_dc Adobe 15.008.20082 (including) 15.009.20069 (excluding)
Acrobat_reader Adobe 10.0 (including) 10.1.15 (including)
Acrobat_reader Adobe 11.0.0 (including) 11.0.12 (including)
Acrobat_reader_dc Adobe 15.006.30060 (including) 15.006.30094 (excluding)
Acrobat_reader_dc Adobe 15.008.20082 (including) 15.009.20069 (excluding)

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).