LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22904: RE11S v1.11 was discovered to contain a stack overflow via the pptpUserName parameter in the setWAN function.

RE11S v1.11 was discovered to contain a stack overflow via the pptpUserName parameter in the setWAN function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-22904 is a critical stack overflow reported in RE11S v1.11. A network-accessible parameter can trigger memory corruption, with CVSS indicating potential full compromise of confidentiality, integrity, and availability. Public sources do not confirm active exploitation or a vendor fix.

Executive priority

Prioritize this as urgent for any environment with RE11S v1.11, especially internet-reachable devices. The high CVSS score reflects potential unauthenticated remote compromise. Business urgency depends on whether affected devices exist and whether their management surfaces are exposed.

Technical view

The CVE describes a CWE-120 stack-based buffer overflow in the setWAN function via the pptpUserName parameter in RE11S v1.11. CVSS 3.1 is 9.8: network attack vector, low complexity, no privileges, no user interaction, and high C/I/A impact.

Likely exposure

Organizations using RE11S v1.11 should treat exposed management or WAN configuration interfaces as high risk. The CVE record does not provide CPEs or complete vendor/product metadata, so asset identification may require manual inventory review.

Exploitation context

The CVE is not listed in KEV in the provided bundle. A public GitHub reference exists for the vulnerability, but the supplied sources do not prove real-world exploitation. Do not assume exploitation until confirmed by KEV, vendor, or threat intelligence sources.

Researcher notes

Public data is sparse: affected vendor/product fields are listed as n/a, while references point to Edimax and a GitHub report. The vulnerability description is concise and does not name a patch. Further validation should rely on vendor confirmation and controlled, authorized testing only.

Mitigation direction

  • Identify any RE11S v1.11 devices in inventory.
  • Check Edimax and device support channels for firmware or security guidance.
  • Restrict network access to device management interfaces.
  • Disable unnecessary remote administration where possible.
  • Monitor logs for abnormal WAN configuration changes or device instability.

Validation and detection

  • Confirm device model and firmware version from trusted inventory or admin interface.
  • Verify whether pptpUserName-based WAN configuration is reachable from untrusted networks.
  • Review vendor advisories for patched firmware or documented mitigations.
  • Check perimeter exposure for management services associated with affected devices.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
4

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-120: 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-22904 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
3Source 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-22904Attack 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-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.