dbcve.org
Mac Os XOperating system · Apple

CVE-2018-4346

MEDIUM · 5.5 CVSS v3.0 Published 2019-04-03
Fix available
A fix is available. Upgrade to 10.14 or later.
See remediation →
58/100
Remediation priority · Elevated
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
A validation issue existed which allowed local file access. This was addressed with input sanitization. This issue affected versions prior to macOS Mojave 10.14.

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 validation issue in macOS versions prior to 10.14 allowed local file access through insufficient input sanitization. An attacker with local access could potentially read or access files outside intended boundaries due to improper validation of file path inputs.

MitigationUpgrade to macOS Mojave 10.14 or later, which includes the input sanitization fix. For systems that cannot be upgraded, review and restrict file system permissions to limit exposure.

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
Mac Os XOperating system
Affected:< 10.14

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Check installed macOS version
    Open Terminal and run 'sw_vers -productVersion' or go to Apple menu > About This Mac to view the macOS version number
    Affected if The version is lower than 10.14 (for example, 10.13.x, 10.12.x, etc.)
  2. Verify the system is not running macOS Mojave or later
    Compare the version number from step 1 against the fixed release 10.14
    Affected if The installed version starts with 10.13, 10.12, 10.11, or any version string numerically less than 10.14
  3. Identify if the system has untrusted local users or shared access
    Review system preferences under Users & Groups to determine if multiple local accounts exist or if the machine has screen sharing/file sharing enabled
    Affected if Multiple local users exist or file sharing services are enabled on a vulnerable macOS version

The environment is affected if the installed macOS version is numerically less than 10.14, since the vulnerability exists in versions prior to macOS Mojave which introduced the input sanitization fix.

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 10.14 or later
Fixed in 10.14
Interim mitigation

Upgrade to macOS Mojave 10.14 or later, which includes the input sanitization fix. For systems that cannot be upgraded, review and restrict file system permissions to limit exposure.

Fix this in Mac Os X Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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