# CVE-2022-40708: Information disclosure in Trend Micro Deep Security

> A local attacker with low-privileged code execution can exploit an out-of-bounds read in Trend Micro Deep Security to disclose sensitive information.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-2g39-c72r-5g49

## What is CVE-2022-40708?

CVE-2022-40708 is a low-severity vulnerability in Trend Micro Deep Security, published on 28 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-40708?

It affects 1 product.


Products: Trendmicro Deep Security Agent.

## How do I fix CVE-2022-40708?

No fix has been published for CVE-2022-40708 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-40708 being exploited?

There is no known exploitation of CVE-2022-40708 in the wild and no public exploit code.

## Other vulnerabilities in Trend Micro Deep Security

- [CVE-2024-51503](https://insights.sbomify.com/CVE-2024-51503/): Command injection in Trend Micro Deep Security (high 8.0)
- [CVE-2025-30640](https://insights.sbomify.com/CVE-2025-30640/): Privilege escalation in Trend Micro Deep Security (high 7.8)
- [CVE-2025-30641](https://insights.sbomify.com/CVE-2025-30641/): Privilege escalation in Trend Micro Deep Security (high 7.8)
- [CVE-2024-48903](https://insights.sbomify.com/CVE-2024-48903/): Privilege escalation in Trend Micro Deep Security Agent (high 7.8)
- [CVE-2024-36358](https://insights.sbomify.com/CVE-2024-36358/): Privilege escalation in Trend Micro Deep Security Agent (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40708 and fix it if it is affected.

What it is: CVE-2022-40708 is a low-severity vulnerability in Trend Micro Deep Security, published on 28 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40708 in the wild and no public exploit code.

Affected product: Trend Micro Deep Security. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-40708/ (Markdown: https://insights.sbomify.com/CVE-2022-40708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-40708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-40708
- OSV: https://osv.dev/vulnerability/CVE-2022-40708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-40708/
Summaries are generated and may contain mistakes; the official description above is the record.