# CVE-2017-6039: Hardcoded credentials in Phoenix Broadband Technologies LLC PowerAgent SC3 Site Controller

> Hard-coded passwords in Phoenix Broadband PowerAgent SC3 BMS allow unauthorized access to the device.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-32wr-wj5p-2r78

## What is CVE-2017-6039?

CVE-2017-6039 is a medium-severity vulnerability in Phoenix Broadband Technologies LLC PowerAgent SC3 Site Controller, published on 2 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Use of Hard-Coded Password issue was discovered in Phoenix Broadband PowerAgent SC3 BMS, all versions prior to v6.87. Use of a hard-coded password may allow unauthorized access to the device.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Phoenixbroadband Poweragent Sc3 Bms Firmware.

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

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

## Is CVE-2017-6039 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6039 is a medium-severity vulnerability in Phoenix Broadband Technologies LLC PowerAgent SC3 Site Controller, published on 2 Jun 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-6039 in the wild and no public exploit code.

Affected product: Phoenix Broadband Technologies LLC PowerAgent SC3 Site Controller. 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-6039/ (Markdown: https://insights.sbomify.com/CVE-2017-6039/index.md)
```

## Sources

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

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