dbcve.org
FedoraOperating system · Fedoraproject

CVE-2016-4607

CRITICAL · 9.8 CVSS v3.1 Published 2016-07-22
Fix available
A fix is available. Upgrade to 1.1.29 / 2.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
libxslt in Apple iOS before 9.3.3, OS X before 10.11.6, iTunes before 12.4.2 on Windows, iCloud before 5.2.1 on Windows, tvOS before 9.2.2, and watchOS before 2.2.2 allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors, a different vulnerability than CVE-2016-4608, CVE-2016-4609, CVE-2016-4610, and CVE-2016-4612.

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

libxslt contains a memory corruption vulnerability that can be exploited remotely to cause denial of service or potentially achieve code execution. The specific attack vector is not detailed in the available description, which references 'unknown vectors'.

MitigationApply the vendor-supplied patches by updating to iOS 9.3.3+, OS X 10.11.6+, iTunes 12.4.2+, iCloud 5.2.1+, tvOS 9.2.2+, or watchOS 2.2.2+ as appropriate for each affected system.

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
FedoraOperating system
Affected:= 30
LibxsltApplication
Affected:< 1.1.29
Iphone OsOperating system
Affected:< 9.3.3
Mac Os XOperating system
Affected:< 10.11.6
TvosOperating system
Affected:< 9.2.2
WatchosOperating system
Affected:< 2.2.2
IcloudApplication
Affected:< 5.2.1
ItunesApplication
Affected:< 12.4.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if libxslt library is installed
    On Linux: run 'rpm -qa | grep libxslt' (RHEL/Fedora) or 'dpkg -l | grep libxslt' (Debian/Ubuntu). On macOS: run 'brew list libxslt' if using Homebrew, or check via 'ls /usr/lib/libxslt*'
    Affected if No libxslt package or library found means not affected by this specific libxslt flaw
  2. Determine installed libxslt version on Linux
    Run 'rpm -q libxslt' (RHEL/Fedora) or 'dpkg -s libxslt' (Debian/Ubuntu) to retrieve the installed version number
    Affected if Version is lower than 1.1.29 (e.g., 1.1.28, 1.1.27, etc.) indicates vulnerability
  3. Check libxslt version via pkg-config
    Run 'pkg-config --modversion libxslt-1.0' or 'pkg-config --modversion libxslt' if the development package is installed
    Affected if Version shown is below 1.1.29
  4. Verify libxslt version in use by application
    For applications using libxslt, run 'ldd /path/to/application | grep libxslt' to identify the linked library, then check that library's version as shown in step 2
    Affected if Linked libxslt version is below 1.1.29
  5. Check Apple system OS versions
    On Apple devices, check iOS version (Settings > General > About > Version), macOS version (About This Mac), or installed app versions for iTunes/iCloud
    Affected if iOS < 9.3.3, macOS < 10.11.6, iTunes < 12.4.2, iCloud < 5.2.1, tvOS < 9.2.2, or watchOS < 2.2.2

You are affected if libxslt version is below 1.1.29, or if running an unpatched Apple OS or application version listed in the affected range.

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 1.1.29 / 2.2.2 / 5.2.1 or later
Fixed in 1.1.292.2.25.2.1
Interim mitigation

Apply the vendor-supplied patches by updating to iOS 9.3.3+, OS X 10.11.6+, iTunes 12.4.2+, iCloud 5.2.1+, tvOS 9.2.2+, or watchOS 2.2.2+ as appropriate for each affected system.

Recommended fix High confidence

Libxslt 1.1.29 or later; Apple iOS 9.3.3+; macOS 10.11.6+; tvOS 9.2.2+; watchOS 2.2.2+; iCloud 5.2.1+; iTunes 12.4.2+

  1. For Apple devices (iOS, macOS, tvOS, watchOS, iTunes, iCloud): Update to the specified minimum versions via Settings > General > Software Update (iOS/tvOS/watchOS), Mac App Store (macOS/iTunes), or Apple website (iCloud for Windows)
  2. For Linux systems with libxslt: Upgrade libxslt to version 1.1.29 or later via package manager (e.g., dnf/yum update libxslt on Fedora)
  3. For other libxslt users: Obtain libxslt 1.1.29 or later from the official libxslt distribution (https://xmlsoft.org/xslt/)
Caveat Standard OS/application update risks apply (ensure backups before updating)

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

Fix this in Fedora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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