# CVE-2025-49164: Hardcoded credentials in VIP1113

> Arris VIP1113 devices contain a hardcoded firmware decryption key, allowing attackers to decrypt firmware and potentially execute arbitrary code.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/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:** 2 Jun 2025
- **Updated:** 3 Jun 2025
- **Also known as:** GHSA-q9c3-7qmh-545w

## What is CVE-2025-49164?

CVE-2025-49164 is a medium-severity vulnerability in Arris VIP1113, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Arris VIP1113 devices through 2025-05-30 with KreaTV SDK have a firmware decryption key of cd1c2d78f2cba1f73ca7e697b4a485f49a8a7d0c8b0fdc9f51ced50f2530668a.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-49164?


## How do I fix CVE-2025-49164?

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

## Is CVE-2025-49164 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49164 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49164 and fix it if it is affected.

What it is: CVE-2025-49164 is a medium-severity vulnerability in Arris VIP1113, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49164 exists.

Affected product: Arris VIP1113. 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-2025-49164/ (Markdown: https://insights.sbomify.com/CVE-2025-49164/index.md)
```

## Sources

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

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