# CVE-2017-11379: Other in Trend Micro Deep Discovery Director

> Attackers can bypass integrity checks on configuration and database backups due to missing signatures, potentially allowing unauthorized modifications.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xwf9-ppp5-89qf

## What is CVE-2017-11379?

CVE-2017-11379 is a high-severity vulnerability in Trend Micro Deep Discovery Director, published on 1 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Configuration and database backup archives are not signed or validated in Trend Micro Deep Discovery Director 1.1.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2017-11379?

It affects 1 product.


Products: Trendmicro Deep Discovery Director.

## How do I fix CVE-2017-11379?

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

## Is CVE-2017-11379 being exploited?

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

## Other vulnerabilities in Trend Micro Deep Discovery Director

- [CVE-2017-11380](https://insights.sbomify.com/CVE-2017-11380/): Hardcoded credentials in Trend Micro Deep Discovery Director (critical 9.8)
- [CVE-2017-11381](https://insights.sbomify.com/CVE-2017-11381/): Command injection in Trend Micro Deep Discovery Director (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11379 and fix it if it is affected.

What it is: CVE-2017-11379 is a high-severity vulnerability in Trend Micro Deep Discovery Director, published on 1 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11379 in the wild and no public exploit code.

Affected product: Trend Micro Deep Discovery Director. 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-2017-11379/ (Markdown: https://insights.sbomify.com/CVE-2017-11379/index.md)
```

## Sources

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

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