CVE-2010-1254
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 · uneditedThe installation for Microsoft Open XML File Format Converter for Mac sets insecure ACLs for the /Applications folder, which allows local users to execute arbitrary code by replacing the executable with a Trojan Horse, aka "Mac Office Open XML Permissions Vulnerability."
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 installer for Microsoft Open XML File Format Converter for Mac incorrectly sets Access Control Lists (ACLs) on the /Applications folder, permitting any local user to modify or replace executable files in that directory. This allows privilege escalation via Trojan Horse attacks where malicious executables can be substituted for legitimate applications.
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 dataall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:M/Au:N/C:C/I:C/A:C
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 if Open XML File Format Converter is installedRun: ls /Applications | grep -i 'Open XML' or check /Library/Application Support/Microsoft for converter remnantsAffected if The converter or its installer remnants are present on the system
-
Examine ACLs on /Applications folderRun: ls -lOd /Applications or ls -le /Applications | head -20 to view ACL entriesAffected if ACLs show any:allow write or world:writable permissions allowing non-admin users modify access
-
Verify group ownership and permissions on /ApplicationsRun: ls -lnd /Applications to check owner, group, and mode. Run: chmod -A 'everyone deny write' /Applications to test current ACL state if neededAffected if The directory shows group or world write permissions, or ACLs do not restrict write access to admin users only
-
Check for unauthorized modifications in /ApplicationsReview file integrity baseline for /Applications contents or run: find /Applications -type f -perm -002 to find world-writable executablesAffected if Any executable files in /Applications are writable by non-privileged users
A user is affected if the Open XML File Format Converter was ever installed and the /Applications folder ACLs permit write access by non-administrative users, allowing potential privilege escalation through executable substitution.
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 dataCorrect the ACLs on /Applications folder to restrict write access to administrators only, then either reinstall the converter with proper permissions or audit/re-secure the /Applications directory.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1254 — 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-2010-1254 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