# CVE-2017-6339: Weak cryptography in n/a

> Attackers can download weakly encrypted private keys to decrypt HTTPS traffic, compromising confidentiality on Trend Micro IWSVA appliances.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8jrh-xx3q-344c

## What is CVE-2017-6339?

CVE-2017-6339 is a medium-severity vulnerability in n/a, published on 5 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Trend Micro InterScan Web Security Virtual Appliance (IWSVA) 6.5 before CP 1746 mismanages certain key and certificate data. Per IWSVA documentation, by default, IWSVA acts as a private Certificate Authority (CA) and dynamically generates digital certificates that are sent to client browsers to complete a secure passage for HTTPS connections. It also allows administrators to upload their own certificates signed by a root CA. An attacker with low privileges can download the current CA certificate and Private Key (either the default ones or ones uploaded by administrators) and use those to decrypt HTTPS traffic, thus compromising confidentiality. Also, the default Private Key on this appliance is encrypted with a very weak passphrase. If an appliance uses the default Certificate and Private Key provided by Trend Micro, an attacker can simply download these and decrypt the Private Key using the default/weak passphrase.

Weakness: CWE-521 (Weak Password Requirements), CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Trendmicro Interscan Web Security Virtual Appliance.

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

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

## Is CVE-2017-6339 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6339 exists.

Public exploit code:

- Trend Micro InterScan Web Security Virtual Appliance (IWSVA) 6.5 SP2 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2016-9269](https://insights.sbomify.com/CVE-2016-9269/): Command injection in n/a (critical 9.9)
- [CVE-2020-8465](https://insights.sbomify.com/CVE-2020-8465/): Auth bypass in Trend Micro InterScan Web Security Virtual Appliance (critical 9.8)
- [CVE-2020-8466](https://insights.sbomify.com/CVE-2020-8466/): Command injection in Trend Micro InterScan Web Security Virtual Appliance (critical 9.8)
- [CVE-2020-28578](https://insights.sbomify.com/CVE-2020-28578/): Memory corruption in Trend Micro InterScan Web Security Virtual Appliance (critical 9.8)
- [CVE-2020-8606](https://insights.sbomify.com/CVE-2020-8606/): Auth bypass in Trend Micro InterScan Web Security Virtual Appliance (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6339 is a medium-severity vulnerability in n/a, published on 5 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-6339 exists.

Affected product: n/a. 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-6339/ (Markdown: https://insights.sbomify.com/CVE-2017-6339/index.md)
```

## Sources

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

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