LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45669: Tenda i22 V1.0.0.3(4687) was discovered to contain a buffer overflow via the index parameter in the formWif...

Tenda i22 V1.0.0.3(4687) was discovered to contain a buffer overflow via the index parameter in the formWifiMacFilterGet function.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-45669 is a high-severity availability issue in Tenda i22 firmware V1.0.0.3(4687). A network-reachable buffer overflow in a Wi-Fi MAC filter function could crash or disrupt the device. The sources do not show confirmed active exploitation or a named vendor fix.

Executive priority

Treat this as a near-term network infrastructure risk where affected devices support business connectivity. The main business concern is service disruption, not data theft based on the cited CVSS impacts. Prioritize exposed or business-critical devices first.

Technical view

The CVE describes a CWE-120 buffer overflow in the formWifiMacFilterGet function, triggered through the index parameter. CVSS 3.1 is 7.5: network attack vector, low complexity, no privileges, no user interaction, and high availability impact with no stated confidentiality or integrity impact.

Likely exposure

Exposure is likely limited to organizations running Tenda i22 devices on firmware V1.0.0.3(4687), especially where the relevant management interface is reachable from untrusted networks. The CVE record’s structured affected-product fields are incomplete, so asset confirmation is important.

Exploitation context

The CVE and public reference indicate a remotely reachable denial-of-service style risk. The provided bundle marks CISA KEV as false, and no cited source confirms active exploitation in the wild. No exploit status beyond the public vulnerability report is established here.

Researcher notes

The source evidence identifies the vulnerable function and parameter but provides incomplete normalized affected-product metadata. Avoid broad Tenda assumptions beyond i22 V1.0.0.3(4687). No official patch information, KEV listing, or confirmed exploitation is present in the supplied sources.

Mitigation direction

  • Inventory Tenda i22 devices and identify firmware V1.0.0.3(4687).
  • Check Tenda support channels for firmware updates or official mitigation guidance.
  • Restrict device management access to trusted administrative networks only.
  • Prioritize replacement or isolation if vendor remediation cannot be verified.
  • Monitor affected devices for unexplained crashes or service disruption.

Validation and detection

  • Confirm device model and firmware from trusted asset records or management consoles.
  • Review whether management interfaces are exposed to untrusted networks.
  • Check vendor advisories for any fixed firmware or mitigation notes.
  • Correlate device instability with traffic to administrative services.
  • Document affected assets and remediation status for vulnerability tracking.
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-2022-45669 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
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
0Timeline events
0ADP providers
2Source links

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-45669Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
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.