# CVE-2017-20214: FLIR Thermal Camera F/FC/PT/D firmware version 8.0.0.64 Hard-Coded SSH Credentials Vulnerability

> Attackers can use hard-coded SSH credentials to gain unauthorized remote access to FLIR thermal cameras, potentially executing code or taking over the device.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-mgmw-cpxg-gc2f

## What is CVE-2017-20214?

CVE-2017-20214 is a critical vulnerability in FLIR Thermal Camera F/FC/PT/D, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FLIR Thermal Camera F/FC/PT/D firmware version 8.0.0.64 contains hard-coded SSH credentials that cannot be changed through normal camera operations. Attackers can leverage these persistent, unmodifiable credentials to gain unauthorized remote access to the thermal camera system.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2017-20214 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-20214 is a critical vulnerability in FLIR Thermal Camera F/FC/PT/D, published on 7 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-20214 exists.

Affected product: FLIR Thermal Camera F/FC/PT/D. 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-20214/ (Markdown: https://insights.sbomify.com/CVE-2017-20214/index.md)
```

## Sources

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

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