LiveActive security incident?Get immediate response
CVE Record

CVE-2022-3048: Inappropriate implementation in Chrome OS lockscreen in Google Chrome on Chrome OS prior to 105.0.5195.52 a...

Inappropriate implementation in Chrome OS lockscreen in Google Chrome on Chrome OS prior to 105.0.5195.52 allowed a local attacker to bypass lockscreen navigation restrictions via physical access to the device.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-3048 is a Chrome OS lockscreen weakness fixed before version 105.0.5195.52. Someone with physical access could bypass navigation restrictions while the device was locked. It matters most for shared, kiosk, education, retail, and lost or unattended Chrome OS devices.

Executive priority

Treat this as a targeted physical-access risk, not a mass remote compromise. Patch or retire affected Chrome OS devices promptly, with priority for fleets in public, shared, or mobile settings where unattended access is plausible.

Technical view

The CVE describes an inappropriate implementation in the Chrome OS lockscreen, mapped to CWE-863. The CVSS vector is physical access, low complexity, no privileges or user interaction, unchanged scope, with high confidentiality, integrity, and availability impact. Sources identify Chrome OS before 105.0.5195.52 as affected.

Likely exposure

Exposure is most likely where Chrome OS devices remain below 105.0.5195.52 and can be physically accessed by untrusted people. The provided affected-product metadata is broad, so asset validation should focus on Chrome OS version evidence rather than assuming all Chrome installations are exposed.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. Exploitation requires physical access to the device, reducing internet-scale risk but increasing concern for unattended, shared, or stolen endpoints.

Researcher notes

The public description is concise and does not include implementation detail. Avoid broad Chrome desktop assumptions: the vulnerability is specifically described in Chrome OS lockscreen behavior before 105.0.5195.52. Active exploitation is not supported by the provided sources.

Mitigation direction

  • Update Chrome OS devices to 105.0.5195.52 or later where applicable.
  • Check Google and device-management guidance for any model-specific remediation details.
  • Prioritize shared, kiosk, classroom, retail, and executive-travel Chrome OS devices.
  • Reduce unattended physical access until affected devices are updated.
  • Review lost-device and remote-wipe processes for managed Chrome OS fleets.

Validation and detection

  • Inventory Chrome OS devices and record OS version for each endpoint.
  • Flag devices running Chrome OS versions before 105.0.5195.52.
  • Confirm update status through endpoint or Chrome enterprise management records.
  • Verify lockscreen policies are managed consistently across shared-device groups.
  • Check incident records for lost, stolen, or unattended affected devices.
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-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-3048 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.8 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Incorrect Authorization

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