dbcve.org
XcodeApplication · Apple

CVE-2017-7167

HIGH · 7.8 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 9.2 or later.
See remediation →
81/100
Remediation priority · High
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
An issue was discovered in certain Apple products. Xcode before 9.2 is affected. The issue involves the "ld64" component. A buffer overflow allows remote attackers to execute arbitrary code via crafted source 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

A buffer overflow vulnerability exists in the ld64 linker component of Xcode versions prior to 9.2. The flaw allows remote attackers to execute arbitrary code by supplying specially crafted source code that triggers the overflow during the linking phase of compilation.

MitigationUpgrade Xcode to version 9.2 or later to obtain the patched ld64 linker. Audit build environments to ensure no older vulnerable Xcode versions remain in use.

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
XcodeApplication
Affected:< 9.2

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
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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. Check installed Xcode version
    Run 'xcodebuild -version' in Terminal to display the current Xcode version, or open Xcode and select 'About Xcode' from the Xcode menu
    Affected if The version displayed is below 9.2 (for example, 9.0, 9.1, 8.x, or earlier)
  2. Verify Xcode command line tools version
    Run 'xcode-select -p' to find the Xcode developer directory, then run 'ld -v' or check the ld64 version within that toolchain path
    Affected if The linked ld64 or Xcode version is earlier than 9.2
  3. Scan for multiple Xcode installations
    Check /Applications folder for multiple Xcode.app instances (such as Xcode.app, Xcode-8.app), and check /Library/Developer for older Xcode archives
    Affected if Any Xcode installation found is version 9.1 or earlier
  4. Check for older Xcode in versioned developer paths
    Inspect directories like /Library/Developer/Xcode/Drafts or ~/Library/Developer/Xcode for older versions, and run 'ls -la' on these paths
    Affected if Any discovered Xcode version is below 9.2

You are affected if any Xcode installation on the system, including command line tools, is version 9.1 or earlier (the vulnerability is in the ld64 linker component of versions prior to 9.2).

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

Upgrade Xcode to version 9.2 or later to obtain the patched ld64 linker. Audit build environments to ensure no older vulnerable Xcode versions remain in use.

Fix this in Xcode Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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