LiveActive security incident?Get immediate response
CVE Record

CVE-2025-57174: An issue was discovered in Siklu Communications Etherhaul 8010TX and 1200FX devices, Firmware 7.4.0 through...

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This vulnerability can let an unauthenticated attacker remotely run commands on affected Siklu Etherhaul wireless backhaul devices. The issue comes from shared hardcoded encryption keys in a service exposed on TCP port 555. For organizations using these devices in telecom, ISP, or enterprise backhaul roles, compromise could affect confidentiality, integrity, and availability of network infrastructure.

Executive priority

Treat as urgent for any organization operating affected Siklu Etherhaul devices. The issue is remotely reachable, unauthenticated, and rated CVSS 9.8. Prioritize exposure reduction immediately while confirming vendor remediation options.

Technical view

CVE-2025-57174 affects Siklu Etherhaul 8010TX and 1200FX firmware 7.4.0 through 10.7.3, and possibly other shared-firmware Etherhaul devices. The rfpiped service on TCP/555 uses static AES keys hardcoded in the binary and shared across devices, enabling crafted encrypted packets to execute arbitrary commands without authentication. It is described as a failed patch for CVE-2017-7318.

Likely exposure

Exposure is highest where affected Etherhaul devices have TCP port 555 reachable from untrusted networks. Devices used for wireless backhaul may sit at network edges, increasing business impact if management or service ports are not tightly filtered.

Exploitation context

The CVE record and referenced research describe unauthenticated remote command execution. The source bundle does not show CISA KEV listing or confirmed active exploitation. Public technical research is referenced, so defenders should assume capable attackers can study the issue.

Researcher notes

The source data lists vendor and product fields as n/a but the description names Etherhaul 8010TX and 1200FX. Scope may include other Etherhaul devices sharing firmware, but that is not confirmed. No official patch details are included in the provided sources.

Mitigation direction

  • Check Siklu guidance for fixed firmware or official mitigation.
  • Restrict TCP port 555 to trusted management networks only.
  • Block internet access to device management and service ports.
  • Isolate affected backhaul devices from critical internal systems.
  • Prioritize replacement or upgrade if no vendor fix is available.

Validation and detection

  • Inventory Siklu Etherhaul 8010TX and 1200FX devices.
  • Confirm firmware versions, especially 7.4.0 through 10.7.3.
  • Identify any reachable TCP port 555 exposure.
  • Review perimeter rules protecting device management networks.
  • Monitor affected devices for unexplained configuration or command activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-321: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-57174 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-57174Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-321 · source CWE mapping

Use of Hard-coded Cryptographic Key

Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.