Trend Micro Apex One and Worry-Free Business Security Remote Code Execution
CVE-2023-41179 is a high-severity improper control of generation of code vulnerability in Trend Micro Apex One from Trend Micro, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. The record lists versions 14.0.0.12380, 14.0.12637 as the first without the flaw, so updating Trend Micro Apex One to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on September 21, 2023, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Trend Micro Apex One to 14.0.0.12380 or 14.0.12637, whichever matches your release line, or a later version.
- Update Trend Micro Worry-Free Business Security to 10.0 SP1 Build 2495 or a later version.
- Update Trend Micro Worry-Free Business Security Services to 6.7.3578 / 14.3.1105 or a later version.
- CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Trend Micro | Trend Micro Apex One | 2019 (14.0) up to, but not including, 14.0.0.12380; SaaS up to, but not including, 14.0.12637 | 14.0.0.12380, 14.0.12637 |
| Trend Micro | Trend Micro Worry-Free Business Security | 10.0 SP1 up to, but not including, 10.0 SP1 Build 2495 | 10.0 SP1 Build 2495 |
| Trend Micro | Trend Micro Worry-Free Business Security Services | SaaS up to, but not including, 6.7.3578 / 14.3.1105 | 6.7.3578 / 14.3.1105 |
| Trend Micro | apex_one | 2019 | Not stated |
| Trend Micro | worry-free_business_security | 10.0 | Not stated |
| Trend Micro | worry-free_business_security_services | all versions | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- HighAdministrator-level access is required first.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | NVD |
| CVSS 3.1 | 7.2 | High | CISA (ADP) |
Official description
A vulnerability in the 3rd party AV uninstaller module contained in Trend Micro Apex One (on-prem and SaaS), Worry-Free Business Security and Worry-Free Business Security Services could allow an attacker to manipulate the module to execute arbitrary commands on an affected installation. Note that an attacker must first obtain administrative console access on the target system in order to exploit this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Control of Generation of Code
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
How developers prevent this class of flaw
- Refactor your program so that you do not have to dynamically generate code.
- Run your code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Use dynamic tools and techniques that interact with the product using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The product's operation may slow down, but it should not become unstable, crash, or generate incorrect results.
More Improper Control of Generation of Code vulnerabilities (CWE-94)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- jvn.jp/en/vu/JVNVU90967486/Third Party Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-41179US Government Resource
Other vulnerabilities in Trend Micro Apex One
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
Recent Improper Control of Generation of Code vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.