# CVE-2015-4400: Information disclosure in n/a

> Remote attackers can obtain sensitive wireless network configuration data from Ring video doorbells by pressing the setup button and exploiting the Wi-Fi module API.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 6 Feb 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jpmj-x4f8-38xj

## What is CVE-2015-4400?

CVE-2015-4400 is a medium-severity vulnerability in n/a, published on 6 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Ring (formerly DoorBot) video doorbells allow remote attackers to obtain sensitive information about the wireless network configuration by pressing the set up button and leveraging an API in the GainSpan Wi-Fi module.

Weakness: CWE-255

## Which versions are affected by CVE-2015-4400?

It affects 1 product.


Products: Ring Ring Firmware.

## How do I fix CVE-2015-4400?

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

## Is CVE-2015-4400 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4400 and fix it if it is affected.

What it is: CVE-2015-4400 is a medium-severity vulnerability in n/a, published on 6 Feb 2018. 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-2015-4400 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-2015-4400/ (Markdown: https://insights.sbomify.com/CVE-2015-4400/index.md)
```

## Sources

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

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