CVE Vulnerabilities

CVE-2022-40709

Out-of-bounds Read

Published: Sep 28, 2022 | Modified: Feb 27, 2024
CVSS 3.x
3.3
LOW
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

An Out-of-bounds read vulnerability in Trend Micro Deep Security 20 and Cloud One - Workload Security Agent for Windows could allow a local attacker to disclose sensitive information on affected installations. Please note: an attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit these vulnerabilities. This vulnerability is similar to, but not identical to CVE-2022-40707 and 40708.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Deep_security_agent Trendmicro 20.0 (including) 20.0 (including)
Deep_security_agent Trendmicro 20.0-update1337 (including) 20.0-update1337 (including)
Deep_security_agent Trendmicro 20.0-update1559 (including) 20.0-update1559 (including)
Deep_security_agent Trendmicro 20.0-update158 (including) 20.0-update158 (including)
Deep_security_agent Trendmicro 20.0-update167 (including) 20.0-update167 (including)
Deep_security_agent Trendmicro 20.0-update1681 (including) 20.0-update1681 (including)
Deep_security_agent Trendmicro 20.0-update173 (including) 20.0-update173 (including)
Deep_security_agent Trendmicro 20.0-update180 (including) 20.0-update180 (including)
Deep_security_agent Trendmicro 20.0-update182 (including) 20.0-update182 (including)
Deep_security_agent Trendmicro 20.0-update1822 (including) 20.0-update1822 (including)
Deep_security_agent Trendmicro 20.0-update183 (including) 20.0-update183 (including)
Deep_security_agent Trendmicro 20.0-update1876 (including) 20.0-update1876 (including)
Deep_security_agent Trendmicro 20.0-update190 (including) 20.0-update190 (including)
Deep_security_agent Trendmicro 20.0-update198 (including) 20.0-update198 (including)
Deep_security_agent Trendmicro 20.0-update2009 (including) 20.0-update2009 (including)
Deep_security_agent Trendmicro 20.0-update208 (including) 20.0-update208 (including)
Deep_security_agent Trendmicro 20.0-update213 (including) 20.0-update213 (including)
Deep_security_agent Trendmicro 20.0-update2204 (including) 20.0-update2204 (including)
Deep_security_agent Trendmicro 20.0-update223 (including) 20.0-update223 (including)
Deep_security_agent Trendmicro 20.0-update224 (including) 20.0-update224 (including)
Deep_security_agent Trendmicro 20.0-update2419 (including) 20.0-update2419 (including)
Deep_security_agent Trendmicro 20.0-update2593 (including) 20.0-update2593 (including)
Deep_security_agent Trendmicro 20.0-update2740 (including) 20.0-update2740 (including)
Deep_security_agent Trendmicro 20.0-update2921 (including) 20.0-update2921 (including)
Deep_security_agent Trendmicro 20.0-update3165 (including) 20.0-update3165 (including)
Deep_security_agent Trendmicro 20.0-update3288 (including) 20.0-update3288 (including)
Deep_security_agent Trendmicro 20.0-update3445 (including) 20.0-update3445 (including)
Deep_security_agent Trendmicro 20.0-update3530 (including) 20.0-update3530 (including)
Deep_security_agent Trendmicro 20.0-update3771 (including) 20.0-update3771 (including)
Deep_security_agent Trendmicro 20.0-update3964 (including) 20.0-update3964 (including)
Deep_security_agent Trendmicro 20.0-update4185 (including) 20.0-update4185 (including)
Deep_security_agent Trendmicro 20.0-update4416 (including) 20.0-update4416 (including)
Deep_security_agent Trendmicro 20.0-update4726 (including) 20.0-update4726 (including)
Deep_security_agent Trendmicro 20.0-update4959 (including) 20.0-update4959 (including)
Deep_security_agent Trendmicro 20.0-update5137 (including) 20.0-update5137 (including)
Deep_security_agent Trendmicro 20.0-update877 (including) 20.0-update877 (including)

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References