CVE Vulnerabilities

CVE-2017-11655

Missing Release of Resource after Effective Lifetime

Published: Jul 26, 2017 | Modified: Oct 06, 2022
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
5 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

A memory leak was found in the way SIPcrack 0.2 handled processing of SIP traffic, because a lines array was mismanaged. A remote attacker could potentially use this flaw to crash long-running sipdump network sniffing sessions.

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