Galaxy Book Go FirmwareOperating system · Samsung

CVE-2023-30695

HIGH · 7.8 CVSS v3.1 Published 2023-08-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds Write vulnerability in SSHDCPAPP TA prior to "SAMSUNG ELECTONICS, CO, LTD. - System Hardware Update - 7/13/2023" in Windows Update for Galaxy book Go, Galaxy book Go 5G, Galaxy book2 Go and Galaxy book2 Pro 360 allows local attacker to execute arbitrary code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Out-of-bounds Write vulnerability in the SSHDCPAPP Trusted Application (TA) allows a local attacker to execute arbitrary code with elevated privileges. This affects specific Samsung Galaxy book models through a vulnerable TA component in the Windows Update system.

MitigationApply the SAMSUNG ELECTRONICS System Hardware Update dated 7/13/2023 or later via Windows Update to patch the vulnerable SSHDCPAPP TA. Organizations should identify affected Galaxy book Go, Galaxy book Go 5G, Galaxy book2 Go, and Galaxy book2 Pro 360 devices and deploy the vendor patch.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Galaxy Book Go FirmwareOperating system
Affected:all versions
Galaxy Book Go 5g FirmwareOperating system
Affected:all versions
Galaxy Book2 Go FirmwareOperating system
Affected:all versions
Galaxy Book2 Pro 360 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Run 'systeminfo' or check the device properties to determine the exact Samsung Galaxy Book model (e.g., Galaxy Book Go, Galaxy Book Go 5G, Galaxy Book2 Go, or Galaxy Book2 Pro 360)
    Affected if The model is NOT one of: Galaxy Book Go, Galaxy Book Go 5G, Galaxy Book2 Go, or Galaxy Book2 Pro 360
  2. Confirm firmware version is unpatched
    Check Windows Update history for the SAMSUNG ELECTRONICS System Hardware Update. Look for an update installed on or after July 13, 2023 that addresses the SSHDCPAPP TA vulnerability
    Affected if No SAMSUNG ELECTRONICS System Hardware Update from 7/13/2023 or later is present in Windows Update history

A user is affected if they own a Samsung Galaxy Book Go, Galaxy Book Go 5G, Galaxy Book2 Go, or Galaxy Book2 Pro 360 device and the vendor hardware update from July 13, 2023 or later has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SAMSUNG ELECTRONICS System Hardware Update dated 7/13/2023 or later via Windows Update to patch the vulnerable SSHDCPAPP TA. Organizations should identify affected Galaxy book Go, Galaxy book Go 5G, Galaxy book2 Go, and Galaxy book2 Pro 360 devices and deploy the vendor patch.

Recommended fix Moderate confidence

System Hardware Update released July 13, 2023 or later via Windows Update

  1. Open Windows Update on the affected device (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to ensure you have the latest patches
  3. Look for and install any 'System Hardware Update' from Samsung, specifically those released on or after July 13, 2023
  4. After installation, verify the update was applied by checking Windows Update history
  5. Confirm the SSHDCPAPP TA vulnerability is addressed - this is typically delivered as part of the Samsung system firmware update bundle

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Galaxy Book Go Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30695 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data