CVE-2007-5847
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 · uneditedRace condition in the CFURLWriteDataAndPropertiesToResource API in Core Foundation in Apple Mac OS X 10.4.11 creates files with insecure permissions, which might allow local users to obtain sensitive information.
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 confidenceThe CFURLWriteDataAndPropertiesToResource API in Core Foundation on Mac OS X 10.4.11 contains a race condition that causes files to be created with insecure permissions, potentially allowing local unprivileged users to read sensitive data.
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= 10.4.11CVSS 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
- None
AV:L/AC:L/Au:N/C:C/I:C/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Mac OS X versionRun 'sw_vers' in Terminal or check System Preferences > About This Mac. Look for build version 9F33 or the exact version 10.4.11.Affected if The system is running Mac OS X 10.4.11 exactly, or any earlier version of Mac OS X 10.4.x.
-
Identify applications using the vulnerable APISearch application codebases and binaries for calls to 'CFURLWriteDataAndPropertiesToResource' using tools like 'strings', 'otool -Tv', or grep. Review any third-party applications that write data to URLs.Affected if Applications on the system invoke the CFURLWriteDataAndPropertiesToResource API to create files.
-
Inspect recently created file permissionsUse 'ls -la' in directories where applications write files. Check the permission bits (e.g., -rw-rw-rw- instead of -rw-------). Run 'stat <filename>' for detailed permission metadata.Affected if Files created by applications using the vulnerable API have overly permissive permissions (e.g., world-readable or group-readable when they should be private).
-
Monitor for unexpected world-readable filesRun 'find / -perm -004 -type f 2>/dev/null' to locate world-readable files, focusing on directories containing sensitive user data such as Documents, Application Support, or configuration files.Affected if Files that should contain sensitive data are unexpectedly world-readable, allowing any local user to read them.
A system is affected if it runs Mac OS X 10.4.11 and any application uses CFURLWriteDataAndPropertiesToResource to create files that end up with insecure permissions visible to unprivileged local users.
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.
From vendor dataUpgrade from Mac OS X 10.4.11 to a supported macOS version, as this vulnerability is in the OS kernel/API layer and cannot be patched in the legacy system itself; implement file permission monitoring as a compensating control if upgrade is not immediately feasible.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-5847 — 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-2007-5847 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