# CVE-2009-5149: Hardcoded credentials in n/a

> Remote attackers can gain administrative access to Arris devices via predictable technician passwords in the web interface.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/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:** 21 Nov 2015
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v79v-rjff-38ph

## What is CVE-2009-5149?

CVE-2009-5149 is a medium-severity vulnerability in n/a, published on 21 Nov 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arris DG860A, TG862A, and TG862G devices with firmware TS0703128_100611 through TS0705125D_031115 have predictable technician passwords, which makes it easier for remote attackers to obtain access via the web management interface, related to a "password of the day" issue.

Weakness: CWE-255

## Which versions are affected by CVE-2009-5149?

It affects 1 product.


Products: Arris Na Model 862 Gw Mono Firmware.

## How do I fix CVE-2009-5149?

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

## Is CVE-2009-5149 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7289](https://insights.sbomify.com/CVE-2015-7289/): Hardcoded credentials in n/a (critical 9.3)
- [CVE-2015-7291](https://insights.sbomify.com/CVE-2015-7291/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2015-7290](https://insights.sbomify.com/CVE-2015-7290/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5149 and fix it if it is affected.

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

## Sources

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

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