LiveActive security incident?Get immediate response
CVE Record

CVE-2024-57483: Tenda i24 V2.0.0.5 is vulnerable to Buffer Overflow in the addWifiMacFilter function.

Tenda i24 V2.0.0.5 is vulnerable to Buffer Overflow in the addWifiMacFilter function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-57483 is a critical buffer overflow reported in Tenda i24 firmware V2.0.0.5. The published CVSS vector indicates an unauthenticated network attacker could impact confidentiality, integrity, and availability. Public sources do not name a vendor patch or confirm active exploitation.

Executive priority

Treat as urgent for environments using Tenda i24 V2.0.0.5, especially if reachable from untrusted networks. Prioritize inventory and exposure reduction now, while checking vendor guidance for a confirmed fix.

Technical view

The issue is described as a CWE-120 buffer overflow in the addWifiMacFilter function of Tenda i24 V2.0.0.5. CVSS 3.1 is 9.8 with AV:N/AC:L/PR:N/UI:N and high CIA impact. The CVE record’s affected-product metadata is incomplete, but the description identifies Tenda i24 V2.0.0.5.

Likely exposure

Organizations using Tenda i24 access points running firmware V2.0.0.5 are the relevant population. Risk is higher if device administration or vulnerable services are reachable from untrusted networks. The provided sources do not clarify default exposure or internet prevalence.

Exploitation context

No CISA KEV listing is provided, and the sources do not state active exploitation. A public researcher reference exists, but this assessment does not rely on or repeat weaponizable details. The CVSS vector suggests exploitation may be remote and require no authentication.

Researcher notes

Evidence is limited to the CVE description, CVSS data, CWE classification, and a public gist reference. The CVE affected-product fields are not well populated. No patch, workaround, or exploitation-in-the-wild confirmation is present in the provided sources.

Mitigation direction

  • Identify any Tenda i24 devices and confirm firmware versions.
  • Check Tenda or device supplier guidance for firmware updates or advisories.
  • Remove affected devices from untrusted network exposure where feasible.
  • Restrict administrative access to trusted management networks.
  • Replace or retire devices if no vendor remediation is available.

Validation and detection

  • Inventory wireless access points for Tenda i24 models.
  • Verify whether firmware version V2.0.0.5 is installed.
  • Review firewall rules for external or untrusted access paths.
  • Monitor CVE and vendor sources for patch information.
  • Document compensating controls for any affected device retained.
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-57483 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: noneAutomatable: 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-2024-57483Attack 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.