CVE-2019-6203
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 · uneditedA logic issue was addressed with improved state management. This issue is fixed in iOS 12.2, macOS Mojave 10.14.4, tvOS 12.2. An attacker in a privileged network position may be able to intercept network traffic.
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 confidenceThis is a logic vulnerability in Apple's state management for network connections, allowing an attacker with privileged network position (man-in-the-middle) to intercept network traffic. The flaw affects iOS, macOS, and tvOS prior to their 12.2 versions, enabling traffic interception due to improper handling of network state.
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< 12.2< 10.14.4< 12.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS versionGo to Settings > General > About on the iOS device and look at the 'Version' fieldAffected if The version shown is less than 12.2 (for example, 12.1.4, 12.1, 11.x, etc.)
-
Check macOS versionClick the Apple menu > About This Mac. The version number is displayed below the macOS name (for example, 10.14.3, 10.14.2, 10.14.1)Affected if The version shown is less than 10.14.4 (for example, 10.14.3 or any 10.14.x version below 10.14.4, or any earlier version like 10.13.x)
-
Check tvOS versionGo to Settings > General > About > Version on the Apple TVAffected if The version shown is less than 12.2 (for example, 12.1, 12.0, 11.x, etc.)
A user is affected if their device runs iOS, macOS, or tvOS with a version number lower than 12.2 (or 10.14.4 for macOS), as this allows a privileged network attacker to intercept their network traffic due to improper state management.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.14.412.2
Apply the vendor-supplied patches by updating to iOS 12.2+, macOS Mojave 10.14.4+, or tvOS 12.2+ to address the state management flaw.
iOS 12.2, macOS Mojave 10.14.4, tvOS 12.2
- For iPhone OS devices: Navigate to Settings > General > Software Update and upgrade to iOS 12.2 or later
- For Mac computers: Navigate to System Preferences > Software Update and upgrade to macOS Mojave 10.14.4 or later
- For Apple TV devices: Navigate to Settings > System > Software Updates and upgrade to tvOS 12.2 or later
- After upgrading, verify the new OS version matches or exceeds the fixed release to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6203 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-6203 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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