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

> Attackers can unlock doors on iStar Ultra systems by replaying or forging messages due to fixed AES keys and lack of authentication.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2p4x-3pfm-qg42

## What is CVE-2017-17704?

CVE-2017-17704 is a high-severity vulnerability in n/a, published on 31 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A door-unlocking issue was discovered on Software House iStar Ultra devices through 6.5.2.20569 when used in conjunction with the IP-ACM Ethernet Door Module. The communications between the IP-ACM and the iStar Ultra is encrypted using a fixed AES key and IV. Each message is encrypted in CBC mode and restarts with the fixed IV, leading to replay attacks of entire messages. There is no authentication of messages beyond the use of the fixed AES key, so message forgery is also possible.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Swhouse Istar Ultra Firmware.

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

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

## Is CVE-2017-17704 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17704 is a high-severity vulnerability in n/a, published on 31 Dec 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-17704 in the wild and no public exploit code.

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-17704/ (Markdown: https://insights.sbomify.com/CVE-2017-17704/index.md)
```

## Sources

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

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