dbcve.org
Watch OsOperating system · Apple

CVE-2015-5919

HIGH · 7.2 CVSS v2.0 Published 2015-10-09
Fix available
A fix is available. Upgrade to after 1.01 or later.
See remediation →
77/100
Remediation priority · High
No privileges 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
GasGauge in Apple watchOS before 2 allows local users to gain privileges or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-5918.

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 · moderate confidence

GasGauge component in Apple watchOS versions before 2 contains a local privilege escalation or denial of service vulnerability. A local attacker can exploit unspecified vectors to achieve privilege escalation or trigger memory corruption leading to DoS. This is a different vulnerability from CVE-2015-5918.

MitigationUpdate Apple Watch devices to watchOS 2.0 or later to remediate this vulnerability. For systems that cannot be updated, consider network segmentation to limit local attack surface and monitor for suspicious local process activity.

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
Watch OsOperating system
Affected:<= 1.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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

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. Check installed watchOS version
    On the paired iPhone, open the Watch app, go to General > About, or on the Apple Watch itself go to Settings > General > About to view the watchOS version number
    Affected if The version number displayed is 1.01 or lower (any version before 2.0)
  2. Confirm Apple Watch model compatibility
    Verify the Apple Watch model by checking the model number on the device back or in the Watch app under General > About > Model
    Affected if The device is an Apple Watch that shipped with or can run watchOS versions prior to 2.0
  3. Assess local attack surface
    Review what third-party apps are installed on the Apple Watch, as the vulnerability requires a local attacker to exploit unspecified vectors within the GasGauge component
    Affected if The watch has third-party apps installed or allows installation of local applications that could potentially interact with system components

A user is affected if their Apple Watch runs watchOS version 1.01 or any earlier version (anything before watchOS 2.0), since the vulnerability exists in the GasGauge component of those versions.

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.

From vendor data
Upgrade available Upgrade to a release after 1.01
Interim mitigation

Update Apple Watch devices to watchOS 2.0 or later to remediate this vulnerability. For systems that cannot be updated, consider network segmentation to limit local attack surface and monitor for suspicious local process activity.

Fix this in Watch Os Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5919 — 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-2015-5919 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