# CVE-2017-14953: Misconfiguration in n/a

> Physically proximate attackers can associate with HikVision cameras via default unencrypted SSID, bypassing wireless security controls.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7x89-5p28-9fvp

## What is CVE-2017-14953?

CVE-2017-14953 is a medium-severity vulnerability in n/a, published on 1 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HikVision Wi-Fi IP cameras, when used in a wired configuration, allow physically proximate attackers to trigger association with an arbitrary access point by leveraging a default SSID with no WiFi encryption or authentication. NOTE: Vendor states that this is not a vulnerability, but more an increase to the attack surface of the product

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Hikvision Ds-2cd2432f-Iw Firmware.

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

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

## Is CVE-2017-14953 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14953 is a medium-severity vulnerability in n/a, published on 1 Dec 2017. 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-2017-14953 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-14953/ (Markdown: https://insights.sbomify.com/CVE-2017-14953/index.md)
```

## Sources

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

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