LiveActive security incident?Get immediate response
CVE Record

CVE-2024-48416: Edimax AC1200 Wi-Fi 5 Dual-Band Router BR-6476AC 1.06 is vulnerable to Buffer Overflow via /goform/fromSetL...

Edimax AC1200 Wi-Fi 5 Dual-Band Router BR-6476AC 1.06 is vulnerable to Buffer Overflow via /goform/fromSetLanDhcpsClientbinding.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-48416 is a high-severity buffer overflow reported in Edimax BR-6476AC firmware 1.06. An attacker on an adjacent network may be able to compromise confidentiality, integrity, and availability. The supplied sources do not identify a vendor patch, workaround, or active exploitation.

Executive priority

Treat this as a high-priority network-edge risk where affected devices exist. Prioritize discovery and exposure reduction first, then patch or replace once vendor guidance is confirmed.

Technical view

The issue is reported as CWE-120 buffer overflow in /goform/fromSetLanDhcpsClientbinding on Edimax AC1200 Wi-Fi 5 Dual-Band Router BR-6476AC 1.06. CVSS 3.1 is 8.8 with adjacent-network attack vector, low complexity, no privileges, no user interaction, and high C/I/A impact.

Likely exposure

Exposure is likely limited to environments running Edimax BR-6476AC firmware 1.06 and reachable from an adjacent network. The CVE metadata affected-product fields are incomplete, so inventory confirmation by router model and firmware is essential.

Exploitation context

The supplied bundle marks KEV as false and provides no cited evidence of active exploitation. A public advisory is referenced, but the provided bundle does not include verified exploit status or vendor remediation details.

Researcher notes

The evidence supports a high-impact adjacent-network buffer overflow, but public metadata is sparse. Affected CPEs are not populated, and the source bundle does not confirm patch status, exploit maturity, or vulnerable parameter details.

Mitigation direction

  • Check Edimax guidance for fixed firmware or official mitigations.
  • Identify and prioritize any BR-6476AC devices running firmware 1.06.
  • Restrict router management access to trusted administrative networks.
  • Disable unnecessary remote administration or exposed router services.
  • Replace unsupported devices if no vendor fix is available.

Validation and detection

  • Inventory Edimax router model and firmware versions.
  • Confirm whether BR-6476AC firmware 1.06 is present.
  • Review network reachability from adjacent or guest networks.
  • Check vendor advisories for patch or mitigation status.
  • Monitor logs for unusual router configuration 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-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-2024-48416 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/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: noTechnical 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
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2024-48416Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/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.