# CVE-2014-8389: Hardcoded credentials in n/a

> Remote attackers can obtain user credentials via crafted HTTP requests due to hard-coded credentials in the embedded Boa web server of AirLive devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 27 Dec 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4xc5-wc24-8f5h

## What is CVE-2014-8389?

CVE-2014-8389 is a critical vulnerability in n/a, published on 27 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cgi-bin/mft/wireless_mft.cgi in AirLive BU-2015 with firmware 1.03.18 16.06.2014, AirLive BU-3026 with firmware 1.43 21.08.2014, AirLive MD-3025 with firmware 1.81 21.08.2014, AirLive WL-2000CAM with firmware LM.1.6.18 14.10.2011, and AirLive POE-200CAM v2 with firmware LM.1.6.17.01 uses hard-coded credentials in the embedded Boa web server, which allows remote attackers to obtain user credentials via crafted HTTP requests.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2014-8389?

It affects 5 products.


Products: Airlive Bu-2015 Firmware, Airlive Bu-3026 Firmware, Airlive Md-3025 Firmware, Airlive Poe-200cam V2 Firmware, Airlive Wl-2000cam Firmware.

## How do I fix CVE-2014-8389?

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

## Is CVE-2014-8389 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2279](https://insights.sbomify.com/CVE-2015-2279/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8389 and fix it if it is affected.

What it is: CVE-2014-8389 is a critical vulnerability in n/a, published on 27 Dec 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-2014-8389 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-2014-8389/ (Markdown: https://insights.sbomify.com/CVE-2014-8389/index.md)
```

## Sources

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

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