LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3057: Inappropriate implementation in iframe Sandbox in Google Chrome prior to 105.0.5195.52 allowed a remote att...

Inappropriate implementation in iframe Sandbox in Google Chrome prior to 105.0.5195.52 allowed a remote attacker to leak cross-origin data via a crafted HTML page.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Chrome flaw could let a malicious webpage bypass expected iframe sandbox protections and expose cross-origin data. The user would need to open a crafted page. It is not listed in CISA KEV, and the provided sources do not show active exploitation.

Executive priority

Treat as a standard browser patching priority, not an emergency, unless legacy Chrome remains widely deployed. User interaction is required, but browser flaws are exposed to routine web activity.

Technical view

CVE-2022-3057 is an inappropriate iframe Sandbox implementation issue in Google Chrome before 105.0.5195.52. The CVE describes remote, unauthenticated exploitation requiring user interaction through crafted HTML. The record maps to CWE-352, though the description emphasizes cross-origin data leakage.

Likely exposure

Exposure is mainly workstations or managed browsers running Google Chrome earlier than 105.0.5195.52. Gentoo and Fedora advisories indicate distribution package relevance, but the bundle does not name broader affected products.

Exploitation context

The known attack path is web-based: a user visits attacker-controlled HTML. No KEV listing or supplied source confirms exploitation in the wild. Public details are limited, so avoid assuming weaponized exploit availability.

Researcher notes

The CVSS vector in the bundle lists integrity impact, while the description says cross-origin data leakage. The source bundle gives limited technical detail and no exploit telemetry. Validate exposure by version and vendor package state rather than exploit testing.

Mitigation direction

  • Update Google Chrome to 105.0.5195.52 or later.
  • Apply relevant Gentoo or Fedora Chromium/Chrome security updates where applicable.
  • Prioritize managed browser fleets and high-risk user groups.
  • Check vendor guidance for any platform-specific package instructions.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Flag any Chrome installation below 105.0.5195.52.
  • Confirm Linux package managers show current fixed vendor packages.
  • Review browser management reports for delayed or failed updates.
Prepared
Confidence
high
Sources
6

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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-3057 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
5Source 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-3057Attack 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

Source materials

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-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.