CVE-2022-22336

IBM Sterling External Authentication Server and IBM Sterling Secure Proxy 6.0.3.0, 6.0.2.0, and 3.4.3.2 could allow a remote user to consume resources causing a denial of service due to a resource leak. IBM X-Force ID: 219395.

Weakness

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.

Affected Software

Name	Vendor	Start Version	End Version
Sterling_external_authentication_server	Ibm	3.4.3.2 (including)	3.4.3.2 (including)
Sterling_external_authentication_server	Ibm	6.0.2.0 (including)	6.0.2.0 (including)
Sterling_external_authentication_server	Ibm	6.0.3.0 (including)	6.0.3.0 (including)
Sterling_secure_proxy	Ibm	3.4.3.2 (including)	3.4.3.2 (including)
Sterling_secure_proxy	Ibm	6.0.2 (including)	6.0.2 (including)
Sterling_secure_proxy	Ibm	6.0.3.0 (including)	6.0.3.0 (including)

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.

NVD	https://nvd.nist.gov/vuln/detail/CVE-2022-22336
CWE	https://cwe.mitre.org/data/definitions/401.html

Missing Release of Memory after Effective Lifetime

Weakness

Affected Software

Potential Mitigations

References