Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2017-5507

Missing Release of Resource after Effective Lifetime

Published: Mar 24, 2017 | Modified: Nov 21, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
7.8 HIGH
AV:N/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
RedHat/V3
4.4 MODERATE
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
Ubuntu
LOW
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2017-5507
CWEhttps://cwe.mitre.org/data/definitions/772.html

Memory leak in coders/mpc.c in ImageMagick before 6.9.7-4 and 7.x before 7.0.4-4 allows remote attackers to cause a denial of service (memory consumption) via vectors involving a pixel cache.

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
Imagemagick Imagemagick 7.0.1-0 (including) 7.0.1-0 (including)
Imagemagick Imagemagick 7.0.1-1 (including) 7.0.1-1 (including)
Imagemagick Imagemagick 7.0.1-2 (including) 7.0.1-2 (including)
Imagemagick Imagemagick 7.0.1-3 (including) 7.0.1-3 (including)
Imagemagick Imagemagick 7.0.1-4 (including) 7.0.1-4 (including)
Imagemagick Imagemagick 7.0.1-5 (including) 7.0.1-5 (including)
Imagemagick Imagemagick 7.0.1-6 (including) 7.0.1-6 (including)
Imagemagick Imagemagick 7.0.1-7 (including) 7.0.1-7 (including)
Imagemagick Imagemagick 7.0.1-8 (including) 7.0.1-8 (including)
Imagemagick Imagemagick 7.0.1-9 (including) 7.0.1-9 (including)
Imagemagick Imagemagick 7.0.1-10 (including) 7.0.1-10 (including)
Imagemagick Imagemagick 7.0.2-0 (including) 7.0.2-0 (including)
Imagemagick Imagemagick 7.0.2-1 (including) 7.0.2-1 (including)
Imagemagick Imagemagick 7.0.2-2 (including) 7.0.2-2 (including)
Imagemagick Imagemagick 7.0.2-3 (including) 7.0.2-3 (including)
Imagemagick Imagemagick 7.0.2-4 (including) 7.0.2-4 (including)
Imagemagick Imagemagick 7.0.2-5 (including) 7.0.2-5 (including)
Imagemagick Imagemagick 7.0.2-6 (including) 7.0.2-6 (including)
Imagemagick Imagemagick 7.0.2-7 (including) 7.0.2-7 (including)
Imagemagick Imagemagick 7.0.2-8 (including) 7.0.2-8 (including)
Imagemagick Imagemagick 7.0.2-9 (including) 7.0.2-9 (including)
Imagemagick Imagemagick 7.0.2-10 (including) 7.0.2-10 (including)
Imagemagick Imagemagick 7.0.3-0 (including) 7.0.3-0 (including)
Imagemagick Imagemagick 7.0.3-1 (including) 7.0.3-1 (including)
Imagemagick Imagemagick 7.0.3-2 (including) 7.0.3-2 (including)
Imagemagick Imagemagick 7.0.3-3 (including) 7.0.3-3 (including)
Imagemagick Imagemagick 7.0.3-4 (including) 7.0.3-4 (including)
Imagemagick Imagemagick 7.0.3-5 (including) 7.0.3-5 (including)
Imagemagick Imagemagick 7.0.3-6 (including) 7.0.3-6 (including)
Imagemagick Imagemagick 7.0.3-7 (including) 7.0.3-7 (including)
Imagemagick Imagemagick 7.0.3-8 (including) 7.0.3-8 (including)
Imagemagick Imagemagick 7.0.3-9 (including) 7.0.3-9 (including)
Imagemagick Imagemagick 7.0.3-10 (including) 7.0.3-10 (including)
Imagemagick Imagemagick 7.0.4-0 (including) 7.0.4-0 (including)
Imagemagick Imagemagick 7.0.4-1 (including) 7.0.4-1 (including)
Imagemagick Imagemagick 7.0.4-2 (including) 7.0.4-2 (including)
Imagemagick Imagemagick 7.0.4-3 (including) 7.0.4-3 (including)
Imagemagick Ubuntu devel *
Imagemagick Ubuntu precise *
Imagemagick Ubuntu trusty *
Imagemagick Ubuntu upstream *
Imagemagick Ubuntu xenial *
Imagemagick Ubuntu yakkety *

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

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use