LiveActive security incident?Get immediate response
CVE Record

CVE-2023-50984: Tenda i29 v1.0 V1.0.0.5 was discovered to contain a buffer overflow via the ip parameter in the spdtstConfi...

Tenda i29 v1.0 V1.0.0.5 was discovered to contain a buffer overflow via the ip parameter in the spdtstConfigAndStart function.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-50984 describes a reported buffer overflow in Tenda i29 v1.0 firmware V1.0.0.5. The public bundle does not provide a CVSS score, confirmed impact, patch status, or active exploitation evidence. Treat affected devices as requiring review, especially if exposed beyond trusted internal networks.

Executive priority

Prioritize identification and exposure reduction over emergency response. If Tenda i29 devices are internet-facing or in sensitive networks, isolate them until vendor guidance or replacement options are confirmed.

Technical view

The issue is described as a buffer overflow involving the ip parameter in the spdtstConfigAndStart function on Tenda i29 v1.0 V1.0.0.5. The provided records do not include CWE mapping, CVSS metrics, authentication requirements, exploit reliability, or vendor remediation details.

Likely exposure

Exposure is limited to environments running Tenda i29 v1.0 firmware V1.0.0.5. Risk is higher where the affected functionality is reachable from untrusted networks, but the bundle does not define affected interfaces, authentication requirements, or default reachability.

Exploitation context

The source bundle includes a researcher reference but no KEV listing and no cited confirmation of active exploitation. Do not assume exploitation in the wild from these sources alone.

Researcher notes

Evidence is sparse: product, firmware version, function, and parameter are named, but severity metrics and exploit prerequisites are missing. Further assessment should focus on reachability, authentication context, memory corruption impact, and whether vendor-maintained firmware exists.

Mitigation direction

  • Check Tenda guidance for i29 v1.0 V1.0.0.5 updates or retirement options.
  • Do not expose affected device management or diagnostic interfaces to untrusted networks.
  • Restrict access to trusted administration networks with firewall or segmentation controls.
  • Replace or isolate devices if no supported firmware or vendor mitigation exists.
  • Monitor network logs for abnormal requests to device diagnostic functions.

Validation and detection

  • Inventory Tenda i29 devices and record firmware version V1.0.0.5.
  • Confirm whether any affected device is reachable from internet or guest networks.
  • Review vendor and CVE records for updated severity, patches, or mitigations.
  • Check access controls around device management and diagnostic functions.
  • Document compensating controls for any device that cannot be updated.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

cve · low confidence lookup

CVE-2023-50984 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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