# CVE-2025-57174: Hardcoded credentials in n/a

> Attackers can execute arbitrary commands on Siklu Etherhaul devices by exploiting hardcoded AES keys in the rfpiped service, bypassing authentication.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 15 Sep 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-6jfw-mx4q-gmhr

## What is CVE-2025-57174?

CVE-2025-57174 is a critical vulnerability in n/a, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Siklu Communications Etherhaul 8010TX and 1200FX devices, Firmware 7.4.0 through 10.7.3 and possibly other previous versions. The rfpiped service listening on TCP port 555 which uses static AES encryption keys hardcoded in the binary. These keys are identical across all devices, allowing attackers to craft encrypted packets that execute arbitrary commands without authentication. This is a failed patch for CVE-2017-7318. This issue may affect other Etherhaul series devices with shared firmware.

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

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


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

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

## Is CVE-2025-57174 being exploited?

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

Public exploit code:

- CVE-2025-57174 Unauthenticated Remote Command Execution (github_poc): https://github.com/semaja22/CVE-2025-57174
- Siklu EtherHaul Series EH-8010 - Remote Command Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57174 is a critical vulnerability in n/a, published on 15 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-57174 exists.

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-2025-57174/ (Markdown: https://insights.sbomify.com/CVE-2025-57174/index.md)
```

## Sources

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

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