LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33130: Insecure default variable initialization of Intel(R) RealSense(TM) ID Solution F450 before version 2.6.0.74...

Insecure default variable initialization of Intel(R) RealSense(TM) ID Solution F450 before version 2.6.0.74 may allow an unauthenticated user to potentially enable information disclosure via physical access.

MediumCVSS 4.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects Intel RealSense ID Solution F450 deployments running versions before 2.6.0.74. With physical access, an unauthenticated person could potentially disclose sensitive information because of insecure default variable initialization. The issue is medium severity, but confidentiality impact is high for exposed biometric or identity systems.

Executive priority

Treat this as a targeted confidentiality risk, not a broad remote emergency. Prioritize remediation where F450 devices handle sensitive identity data or are reachable by visitors, contractors, or other untrusted people. Confirm inventory first, then update and tighten physical access controls.

Technical view

CVE-2021-33130 is CWE-1188 in Intel RealSense ID Solution F450 before 2.6.0.74. CVSS 3.1 is 4.6 with physical attack vector, low complexity, no privileges, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is limited to organizations using Intel RealSense ID Solution F450 versions earlier than 2.6.0.74. Risk is highest where devices are accessible to untrusted people, shared facilities, reception areas, labs, or other locations where physical access is realistic.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates physical access is required, which reduces internet-scale risk but matters for identity, access-control, or biometric deployments in public or semi-public spaces.

Researcher notes

Available evidence is sparse: the CVE names the product, affected version boundary, CWE, CVSS vector, and Intel advisory. No public exploit status, technical root-cause detail, or compensating controls are provided in the source bundle beyond physical-access constraints and the fixed-version boundary.

Mitigation direction

  • Identify all Intel RealSense ID Solution F450 deployments and their installed versions.
  • Update affected deployments to version 2.6.0.74 or later where vendor guidance supports it.
  • Review Intel advisory INTEL-SA-00595 for any environment-specific remediation guidance.
  • Restrict physical access to affected devices until remediation is complete.
  • Prioritize devices protecting sensitive identity, biometric, or access-control workflows.

Validation and detection

  • Confirm whether each RealSense ID F450 is running a version before 2.6.0.74.
  • Verify updated devices report version 2.6.0.74 or later.
  • Check asset records for unmanaged or physically exposed F450 devices.
  • Review physical placement and access controls for affected devices.
  • Document remediation status against Intel advisory INTEL-SA-00595.
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-1188: 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-33130 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
4.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
4.6CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N0.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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) RealSense(TM) ID Solution F450before version 2.6.0.74Listed
Weakness

CWE details

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

CWE-1188 · source CWE mapping

Initialization of a Resource with an Insecure Default

Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.