LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33139: Improper conditions check in firmware for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) p...

Improper conditions check in firmware for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products before version 22.100 may allow an authenticated user to potentially enable denial of service via adjacent access.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects some Intel Wireless Bluetooth and Killer Bluetooth firmware before version 22.100. A nearby authenticated attacker could cause a denial of service. The issue is availability-focused, not data theft or privilege escalation, but it can disrupt affected endpoints that rely on Bluetooth connectivity.

Executive priority

Treat this as a routine endpoint remediation item with moderate urgency. It is not currently supported as actively exploited, but it can affect availability where Bluetooth is business-relevant or where endpoint disruption has operational cost.

Technical view

CVE-2021-33139 is an improper conditions check in Bluetooth firmware, mapped to CWE-754. CVSS 3.1 is 5.7 with adjacent attack vector, low complexity, low privileges, no user interaction, and high availability impact. Affected products are described as some Intel Wireless Bluetooth and Killer Bluetooth products before 22.100.

Likely exposure

Exposure is most likely on laptops, desktops, or managed endpoints using affected Intel or Killer Bluetooth firmware before 22.100. Internet-facing systems are not the primary concern because the CVSS vector requires adjacent access and an authenticated user.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked KEV. Exploitation requires adjacent access and low privileges, limiting broad remote risk. The supported impact is denial of service only.

Researcher notes

Evidence is limited to the CVE record and Intel advisory reference. The vulnerability scope is stated as some products before 22.100, without detailed SKUs in the provided bundle. Validation should focus on asset inventory and version confirmation, not exploit reproduction.

Mitigation direction

  • Update affected Bluetooth firmware or driver packages to version 22.100 or later.
  • Review Intel SA-00604 for exact vendor guidance and product applicability.
  • Prioritize managed endpoint fleets with Intel or Killer Bluetooth hardware.
  • Disable Bluetooth where it is not operationally required, if vendor guidance permits.

Validation and detection

  • Inventory endpoints with Intel Wireless Bluetooth or Killer Bluetooth hardware.
  • Check installed Bluetooth package or firmware versions against 22.100.
  • Confirm affected pre-22.100 versions are remediated or documented as accepted risk.
  • Review support tooling or endpoint management reports for remaining vulnerable systems.
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-754: 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-2021-33139 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
Medium
CVSS
5.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:L/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
5.7CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.7Medium
CVSS 3.1 vector shape for CVE-2021-33139Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:L/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/aIntel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) productsbefore version 22.100Listed
Weakness

CWE details

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

CWE-754 · source CWE mapping

Improper Check for Unusual or Exceptional Conditions

Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.