CVE Vulnerabilities

CVE-2020-7455

Missing Release of Resource after Effective Lifetime

Published: May 13, 2020 | Modified: Jun 05, 2022
CVSS 3.x
5.5
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

In FreeBSD 12.1-STABLE before r360973, 12.1-RELEASE before p5, 11.4-STABLE before r360973, 11.4-BETA1 before p1 and 11.3-RELEASE before p9, the FTP packet handler in libalias incorrectly calculates some packet length allowing disclosure of small amounts of kernel (for kernel NAT) or natd process space (for userspace natd).

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
Freebsd Freebsd 11.3 (including) 11.3 (including)
Freebsd Freebsd 11.3-p1 (including) 11.3-p1 (including)
Freebsd Freebsd 11.3-p2 (including) 11.3-p2 (including)
Freebsd Freebsd 11.3-p3 (including) 11.3-p3 (including)
Freebsd Freebsd 11.3-p4 (including) 11.3-p4 (including)
Freebsd Freebsd 11.3-p5 (including) 11.3-p5 (including)
Freebsd Freebsd 11.3-p6 (including) 11.3-p6 (including)
Freebsd Freebsd 11.3-p7 (including) 11.3-p7 (including)
Freebsd Freebsd 11.3-p8 (including) 11.3-p8 (including)
Freebsd Freebsd 11.4 (including) 11.4 (including)
Freebsd Freebsd 11.4-beta1 (including) 11.4-beta1 (including)
Freebsd Freebsd 12.1 (including) 12.1 (including)
Freebsd Freebsd 12.1-p1 (including) 12.1-p1 (including)
Freebsd Freebsd 12.1-p2 (including) 12.1-p2 (including)
Freebsd Freebsd 12.1-p3 (including) 12.1-p3 (including)
Freebsd Freebsd 12.1-p4 (including) 12.1-p4 (including)

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