# CVE-2017-3834: Hardcoded credentials in Cisco Aironet 1830 Series and 1850 Series Access Points

> Unauthenticated remote attackers can use default SSH credentials to gain complete control of Cisco Aironet Access Points running Mobility Express software.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 6 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c6vq-6rwf-mq8q

## What is CVE-2017-3834?

CVE-2017-3834 is a critical vulnerability in Cisco Aironet 1830 Series and 1850 Series Access Points, published on 6 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Cisco Aironet 1830 Series and Cisco Aironet 1850 Series Access Points running Cisco Mobility Express Software could allow an unauthenticated, remote attacker to take complete control of an affected device. The vulnerability is due to the existence of default credentials for an affected device that is running Cisco Mobility Express Software, regardless of whether the device is configured as a master, subordinate, or standalone access point. An attacker who has layer 3 connectivity to an affected device could use Secure Shell (SSH) to log in to the device with elevated privileges. A successful exploit could allow the attacker to take complete control of the device. This vulnerability affects Cisco Aironet 1830 Series and Cisco Aironet 1850 Series Access Points that are running an 8.2.x release of Cisco Mobility Express Software prior to Release 8.2.111.0, regardless of whether the device is configured as a master, subordinate, or standalone access point. Release 8.2 was the first release of Cisco Mobility Express Software for next generation Cisco Aironet Access Points. Cisco Bug IDs: CSCva50691.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default), CWE-255

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

It affects 1 product.


Products: Cisco Aironet Access Point Firmware.

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

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

## Is CVE-2017-3834 being exploited?

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

## Other vulnerabilities in Cisco Aironet 1830 Series and 1850 Series Access Points

- [CVE-2017-3873](https://insights.sbomify.com/CVE-2017-3873/): Code injection in Cisco Aironet 1800, 2800, and 3800 Series Access Points (high 7.5)
- [CVE-2019-1834](https://insights.sbomify.com/CVE-2019-1834/): Cisco Aironet Series Access Points Denial of Service Vulnerability (high 7.4)
- [CVE-2019-1826](https://insights.sbomify.com/CVE-2019-1826/): Cisco Aironet Series Access Points Quality of Service Denial of Service Vulnerability (medium 6.8)
- [CVE-2019-1829](https://insights.sbomify.com/CVE-2019-1829/): Cisco Aironet Series Access Points Command Injection Vulnerability (medium 6.7)
- [CVE-2019-1835](https://insights.sbomify.com/CVE-2019-1835/): Cisco Aironet Series Access Points Directory Traversal Vulnerability (medium 4.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3834 is a critical vulnerability in Cisco Aironet 1830 Series and 1850 Series Access Points, published on 6 Apr 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-3834 in the wild and no public exploit code.

Affected product: Cisco Aironet 1830 Series and 1850 Series Access Points. 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-3834/ (Markdown: https://insights.sbomify.com/CVE-2017-3834/index.md)
```

## Sources

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

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