LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34326: In ambiot amb1_sdk (aka SDK for Ameba1) before 2022-06-20 on Realtek RTL8195AM devices before 284241d70308f...

In ambiot amb1_sdk (aka SDK for Ameba1) before 2022-06-20 on Realtek RTL8195AM devices before 284241d70308ff2519e40afd7b284ba892c730a3, the timer task and RX task would be locked when there are frequent and continuous Wi-Fi connection (with four-way handshake) failures in Soft AP mode.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw can make affected Realtek RTL8195AM-based devices stop handling key Wi-Fi tasks when Soft AP connection attempts repeatedly fail during handshakes. The business impact is availability: devices may become unreliable or unavailable over the network. The sources do not identify specific downstream products or active exploitation.

Executive priority

Treat this as a high-priority availability risk for affected embedded fleets, not a broad enterprise IT emergency. Prioritize devices that provide safety, access, monitoring, or customer-facing connectivity, because the known impact is loss of availability under network-triggered Wi-Fi failure conditions.

Technical view

CVE-2022-34326 affects ambiot amb1_sdk, also called SDK for Ameba1, before 2022-06-20 on Realtek RTL8195AM devices before commit 284241d70308ff2519e40afd7b284ba892c730a3. Frequent continuous Wi-Fi four-way handshake failures in Soft AP mode can lock timer and RX tasks. CVSS is 7.5, network attack vector, no privileges, availability-only impact.

Likely exposure

Likely exposure is embedded or IoT firmware built with affected Ameba1 SDK versions on Realtek RTL8195AM devices, especially where Soft AP mode is enabled. The CVE source does not enumerate OEM products, so asset owners must verify chipset, SDK lineage, and firmware version with vendors.

Exploitation context

The CVE has a network attack vector and low complexity, but the provided sources do not state active exploitation, and CISA KEV status is false. The issue requires repeated Wi-Fi connection failure conditions in Soft AP mode and impacts availability rather than confidentiality or integrity.

Researcher notes

The public record is sparse: affected downstream vendors and products are not named, and no exploit activity is cited. Researchers should focus on firmware provenance, SDK version confirmation, Soft AP reachability, and defensive regression testing without publishing operational exploit details.

Mitigation direction

  • Identify products using Realtek RTL8195AM and Ameba1 SDK firmware.
  • Update to vendor firmware built after the 2022-06-20 SDK fix point.
  • Check Realtek or AmebaIoT guidance for product-specific remediation.
  • Disable Soft AP mode where it is not operationally required.
  • Prioritize exposed or business-critical devices for replacement or firmware update.

Validation and detection

  • Inventory chipset, SDK version, and firmware build date for candidate devices.
  • Confirm whether Soft AP mode is enabled in production configurations.
  • Review vendor advisories for fixed firmware or SDK provenance.
  • Check operational logs for repeated Wi-Fi handshake failures and device lockups.
  • Validate remediation in a controlled lab before production rollout.
Prepared
Confidence
medium
Sources
4

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-400: 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-34326 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
3Source 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-34326Attack 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-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.