LiveActive security incident?Get immediate response
CVE Record

CVE-2023-50985: Tenda i29 v1.0 V1.0.0.5 was discovered to contain a buffer overflow via the lanGw parameter in the lanCfgSe...

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-50985 is a reported buffer overflow in Tenda i29 v1.0 V1.0.0.5 involving the lanGw setting. The available sources do not provide CVSS scoring, vendor remediation, or confirmed exploitation. Treat this as an exposure-management issue for any deployed Tenda i29 devices until vendor guidance is confirmed.

Executive priority

Prioritize identification and exposure reduction, not emergency response, unless affected devices are internet-accessible or protect sensitive network segments. The absence of CVSS and KEV evidence keeps urgency uncertain.

Technical view

The CVE description says the lanCfgSet function contains a buffer overflow reachable through the lanGw parameter on Tenda i29 v1.0 V1.0.0.5. The structured CVE affected fields are not populated, and no CWE, CVSS vector, patch version, or exploit maturity details are provided in the bundle.

Likely exposure

Exposure likely applies to environments running Tenda i29 v1.0 V1.0.0.5, especially if device administration surfaces are reachable from untrusted networks. The bundle does not identify other affected versions or products.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle. A public GitHub researcher reference exists, but the bundle does not establish active exploitation or provide reliable exploit prevalence.

Researcher notes

Core weakness details are sparse: parameter, function, product, and firmware are named, but impact, authentication requirements, reachable interface, and remediation are not established in the supplied sources. Validate against vendor materials before broad severity claims.

Mitigation direction

  • Check Tenda guidance for patched firmware or official mitigation.
  • Restrict management access to trusted administrative networks only.
  • Remove public internet exposure for affected device interfaces.
  • Segment affected access points from sensitive internal systems.
  • Replace unsupported devices if no vendor fix is available.

Validation and detection

  • Inventory Tenda i29 devices and record firmware versions.
  • Confirm whether any device runs V1.0.0.5.
  • Review firewall rules for exposed management interfaces.
  • Check vendor advisories for remediation status.
  • Document compensating controls where patch status is unclear.
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.

cve · low confidence lookup

CVE-2023-50985 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
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.