# CVE-2019-14332: Weak cryptography in n/a

> D-Link access points use weak SSH ciphers, potentially allowing attackers to bypass security controls or decrypt traffic.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qwr9-mwmg-r8c4, MGASA-2019-0380

## What is CVE-2019-14332?

CVE-2019-14332 is a high-severity vulnerability in n/a, published on 1 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on D-Link 6600-AP and DWL-3600AP Ax 4.2.0.14 21/03/2019 devices. There is use of weak ciphers for SSH such as diffie-hellman-group1-sha1.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2019-14332?

It affects 2 products.


Products: Dlink 6600-Ap Firmware, Dlink Dwl-3600ap Firmware.

## How do I fix CVE-2019-14332?

Apply the vendor's patch.

## Is CVE-2019-14332 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14338](https://insights.sbomify.com/CVE-2019-14338/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-14335](https://insights.sbomify.com/CVE-2019-14335/): Denial of service in n/a (medium 5.5)
- [CVE-2019-14333](https://insights.sbomify.com/CVE-2019-14333/): Denial of service in n/a (medium 5.5)
- [CVE-2019-14334](https://insights.sbomify.com/CVE-2019-14334/): Information disclosure in n/a (medium 5.5)
- [CVE-2019-14336](https://insights.sbomify.com/CVE-2019-14336/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14332 and fix it if it is affected.

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

## Sources

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

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