LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3310: Insufficient policy enforcement in custom tabs in Google Chrome on Android prior to 106.0.5249.62 allowed a...

Insufficient policy enforcement in custom tabs in Google Chrome on Android prior to 106.0.5249.62 allowed an attacker who convinced the user to install an application to bypass same origin policy via a crafted application. (Chromium security severity: Medium)

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affected Google Chrome on Android before 106.0.5249.62. If a user installed a malicious application, that app could abuse Chrome Custom Tabs to bypass same-origin policy, potentially changing web content or actions that should have been isolated.

Executive priority

Treat as a moderate mobile-browser risk. Prioritize patch compliance for managed Android fleets and app-install controls, but this is not supported as actively exploited by the provided evidence.

Technical view

CVE-2022-3310 is insufficient policy enforcement in Chrome Custom Tabs on Android. The CVSS vector indicates network attack surface, low complexity, no privileges, required user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact.

Likely exposure

Exposure is limited to Android devices running Chrome before 106.0.5249.62, especially environments where users can install unmanaged apps. The sources do not identify affected non-Chrome products or specific vulnerable app integrations.

Exploitation context

The provided sources require the attacker to convince the user to install an application. CISA KEV is false in the bundle, and no cited source confirms active exploitation.

Researcher notes

The public description is sparse and references Chromium bug 1240065. Avoid assuming exploit mechanics beyond a crafted Android application abusing Custom Tabs policy enforcement to bypass same-origin policy.

Mitigation direction

  • Update Chrome on Android to 106.0.5249.62 or later.
  • Use MDM or Play policy to enforce Chrome updates.
  • Restrict installation of untrusted Android applications where possible.
  • Check Google Chrome release guidance for any newer vendor direction.

Validation and detection

  • Inventory Android devices and installed Chrome versions.
  • Flag Chrome on Android versions earlier than 106.0.5249.62.
  • Confirm managed devices receive Chrome updates automatically.
  • Review mobile controls for sideloading or unmanaged app installation.
  • Document remaining unmanaged Android device exposure.
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-602: 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-3310 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
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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
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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-3310Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

CWE details

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

CWE-602 · source CWE mapping

Client-Side Enforcement of Server-Side Security

Client-Side Enforcement of Server-Side Security represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.