LiveActive security incident?Get immediate response
CVE Record

CVE-2023-25717: Ruckus Wireless Admin through 10.4 allows Remote Code Execution via an unauthenticated HTTP GET Request, as...

Ruckus Wireless Admin through 10.4 allows Remote Code Execution via an unauthenticated HTTP GET Request, as demonstrated by a /forms/doLogin?login_username=admin&password=password$(curl substring.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-25717 is a critical unauthenticated remote code execution issue in Ruckus Wireless Admin through version 10.4. If the admin interface is reachable, an attacker may be able to execute commands without logging in. CISA KEV listing means known exploitation has been observed.

Executive priority

Treat this as urgent for any environment running Ruckus Wireless Admin through 10.4. The combination of unauthenticated RCE, critical CVSS, and CISA KEV listing creates a high business risk if affected management interfaces are reachable.

Technical view

The CVE describes CWE-94 code injection via an unauthenticated HTTP GET request against Ruckus Wireless Admin through 10.4. CVSS 3.1 is 9.8, network exploitable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. Structured affected-product metadata is incomplete in the bundle.

Likely exposure

Organizations using Ruckus Wireless Admin through 10.4 are potentially exposed, especially where the admin interface is reachable from the internet or untrusted networks. The source bundle does not provide complete CPE or product inventory mappings.

Exploitation context

CISA lists CVE-2023-25717 in the Known Exploited Vulnerabilities catalog, supporting active exploitation status. A public proof-of-concept reference is also cited, but this analysis does not rely on or reproduce exploitation details.

Researcher notes

Evidence supports unauthenticated RCE and known exploitation, but the bundle lacks complete affected CPEs and specific fixed-version details. Validate exposure by product/version and management-plane reachability, then align remediation with the Ruckus bulletin rather than extrapolating fixes.

Mitigation direction

  • Check Ruckus security bulletin 315 for vendor-supported remediation guidance.
  • Identify and prioritize all Ruckus Wireless Admin instances through version 10.4.
  • Restrict admin interface access to trusted management networks only.
  • Monitor affected systems for unexpected administrative activity or command execution indicators.
  • Apply vendor guidance before considering the risk closed.

Validation and detection

  • Inventory Ruckus Wireless Admin versions across network and asset records.
  • Confirm whether any admin interfaces are internet-facing or reachable by untrusted users.
  • Review logs for suspicious unauthenticated admin endpoint activity.
  • Check CISA KEV entry for operational urgency and remediation expectations.
  • Verify remediation status against Ruckus bulletin 315.
Prepared
Reviewed
Confidence
high
Sources
5

Michael Williams reviewed this cited source version on .

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 · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-25717 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
Yes
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
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-25717Attack 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
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-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.