dbcve.org
Galaxy S9 FirmwareOperating system · Samsung

CVE-2019-6741

CRITICAL · 9.3 CVSS v3.1 Published 2019-06-03
Fix available
A fix is available. Upgrade to 2019-01 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Samsung Galaxy S9 prior to January 2019 Security Update (SMR-JAN-2019 - SVE-2018-13467). User interaction is required to exploit this vulnerability in that the target must connect to a wireless network. The specific flaw exists within the captive portal. By manipulating HTML, an attacker can force a page redirection. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-7476.

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

A remote code execution vulnerability exists in the captive portal component of Samsung Galaxy S9 devices running software versions prior to the January 2019 Security Update (SMR-JAN-2019). Attackers can exploit this by manipulating HTML within a captive portal to force a page redirection, allowing arbitrary code execution in the context of the current process. The attack requires user interaction in that the target must connect to a malicious wireless network.

MitigationApply the January 2019 Security Update (SMR-JAN-2019 - SVE-2018-13467) to affected Samsung Galaxy S9 devices to patch the captive portal vulnerability.

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 S9 FirmwareOperating system
Affected:< 2019-01

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

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 device model
    Go to Settings > About Phone > Device name or model number to confirm the device is a Samsung Galaxy S9
    Affected if Device is not a Samsung Galaxy S9 - this specific vulnerability only affects that model
  2. Check firmware version
    Go to Settings > About Phone > Software information and note the Build number or Firmware version
    Affected if Firmware version/build date is prior to January 2019, or build number is earlier than SMR-JAN-2019 release
  3. Confirm captive portal is reachable
    Attempt to connect to a known public Wi-Fi network that triggers a captive portal, or check if the device has ever displayed a captive portal login/redirect page
    Affected if Captive portal functionality has been used - the vulnerability exploits this component when a user connects to a malicious network
  4. Verify security patch level
    Go to Settings > About Phone > Software information > Security patch level
    Affected if Security patch level shows a date earlier than January 2019 or is blank/unknown

The device is affected if it is a Samsung Galaxy S9 with firmware/Build number dated before the January 2019 Security Update and the captive portal feature is present and has been used.

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
Upgrade available Upgrade to 2019-01 or later
Fixed in 2019-01
Interim mitigation

Apply the January 2019 Security Update (SMR-JAN-2019 - SVE-2018-13467) to affected Samsung Galaxy S9 devices to patch the captive portal vulnerability.

Recommended fix High confidence

SMR-JAN-2019 (SVE-2018-13467)

  1. Ensure your Samsung Galaxy S9 is connected to a stable Wi-Fi or cellular network
  2. Go to Settings on the Galaxy S9 device
  3. Navigate to Settings > Software update (or About phone > Software update)
  4. Tap on Check for updates to search for available updates
  5. If the January 2019 Security Update (SMR-JAN-2019) is available, tap Download and install
  6. Wait for the update to download and then tap Install now
  7. Allow the device to restart and complete the installation process
  8. After the update installs, verify the patch level by going to Settings > About phone > Software information and confirm the Security patch level shows January 2019 or later
Caveat Security updates typically have minimal risk; ensure device is charged and backed up before updating

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

Fix this in Galaxy S9 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2019-6741 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