CVE Vulnerabilities

CVE-2022-38178

Missing Release of Memory after Effective Lifetime

Published: Sep 21, 2022 | Modified: May 28, 2025
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
RedHat/V2
RedHat/V3
7.5 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

By spoofing the target resolver with responses that have a malformed EdDSA signature, an attacker can trigger a small memory leak. It is possible to gradually erode available memory to the point where named crashes for lack of resources.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

Affected Software

NameVendorStart VersionEnd Version
BindIsc9.9.12 (including)9.9.13 (including)
BindIsc9.10.7 (including)9.10.8 (including)
BindIsc9.11.3 (including)9.16.32 (including)
BindIsc9.11.3-s1 (including)9.11.3-s1 (including)
BindIsc9.11.3-s4 (including)9.11.3-s4 (including)
BindIsc9.11.5-s3 (including)9.11.5-s3 (including)
BindIsc9.11.5-s5 (including)9.11.5-s5 (including)
BindIsc9.11.5-s6 (including)9.11.5-s6 (including)
BindIsc9.11.6-s1 (including)9.11.6-s1 (including)
BindIsc9.11.7-s1 (including)9.11.7-s1 (including)
BindIsc9.11.8-s1 (including)9.11.8-s1 (including)
BindIsc9.11.12-s1 (including)9.11.12-s1 (including)
BindIsc9.11.14-s1 (including)9.11.14-s1 (including)
BindIsc9.11.19-s1 (including)9.11.19-s1 (including)
BindIsc9.11.21-s1 (including)9.11.21-s1 (including)
BindIsc9.11.27-s1 (including)9.11.27-s1 (including)
BindIsc9.11.29-s1 (including)9.11.29-s1 (including)
BindIsc9.11.35-s1 (including)9.11.35-s1 (including)
BindIsc9.11.37-s1 (including)9.11.37-s1 (including)
BindIsc9.16.8-s1 (including)9.16.8-s1 (including)
BindIsc9.16.11-s1 (including)9.16.11-s1 (including)
BindIsc9.16.13-s1 (including)9.16.13-s1 (including)
BindIsc9.16.21-s1 (including)9.16.21-s1 (including)
BindIsc9.16.32-s1 (including)9.16.32-s1 (including)
Red Hat Enterprise Linux 7RedHatbind-32:9.11.4-26.P2.el7_9.10*
Red Hat Enterprise Linux 8RedHatbind-32:9.11.36-3.el8_6.1*
Red Hat Enterprise Linux 8RedHatbind9.16-32:9.16.23-0.7.el8_6.1*
Red Hat Enterprise Linux 8RedHatbind-32:9.11.36-3.el8_6.1*
Red Hat Enterprise Linux 8.1 Update Services for SAP SolutionsRedHatbind-32:9.11.4-26.P2.el8_1.6*
Red Hat Enterprise Linux 8.2 Extended Update SupportRedHatbind-32:9.11.13-6.el8_2.4*
Red Hat Enterprise Linux 8.4 Extended Update SupportRedHatbind-32:9.11.26-4.el8_4.1*
Red Hat Enterprise Linux 9RedHatbind-32:9.16.23-1.el9_0.1*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 8RedHatredhat-virtualization-host-0:4.5.3-202211170828_8.6*
Bind9Ubuntubionic*
Bind9Ubuntudevel*
Bind9Ubuntuesm-infra/bionic*
Bind9Ubuntuesm-infra/focal*
Bind9Ubuntufocal*
Bind9Ubuntujammy*
Bind9Ubuntukinetic*
Bind9Ubuntutrusty*
Bind9Ubuntuxenial*

Potential Mitigations

  • Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
  • For example, glibc in Linux provides protection against free of invalid pointers.
  • When using Xcode to target OS X or iOS, enable automatic reference counting (ARC) [REF-391].
  • To help correctly and consistently manage memory when programming in C++, consider using a smart pointer class such as std::auto_ptr (defined by ISO/IEC ISO/IEC 14882:2003), std::shared_ptr and std::unique_ptr (specified by an upcoming revision of the C++ standard, informally referred to as C++ 1x), or equivalent solutions such as Boost.

References