CVE-2015-1150
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 Firewall component in Apple OS X Server before 4.1 uses an incorrect pathname in configuration files, which allows remote attackers to bypass network-access restrictions by sending packets for which custom-rule blocking was intended.
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 confidenceThe Firewall component in Apple OS X Server before 4.1 uses an incorrect pathname in configuration files, causing custom firewall rules to fail to load. This allows remote attackers to bypass network-access restrictions by sending packets that custom-rule blocking was intended to filter.
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<= 4.0CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Determine OS X Server versionCheck the installed version of Apple OS X Server (typically via Server app or system_profiler SPApplicationsDataType)Affected if The installed version is 4.0 or earlier (versions <= 4.0)
-
Identify custom firewall rulesLook for any custom firewall rule configuration files in /etc/ipsec or /Library/Application Support/com.apple.serverfirewall/ or check for user-defined firewall rules via /usr/libexec/ApplicationFirewall/socketfilterfwAffected if Custom firewall rules are configured but may not be loading due to the pathname issue
-
Verify firewall configuration file pathsInspect the firewall configuration files in /Library/Server/Firewall/ for incorrect or malformed pathname references that could prevent custom rules from loadingAffected if Configuration files contain incorrect or mismatched path references
-
Test if custom rules are activeRun 'socketfilterfw --listapps' or check active firewall rules to confirm custom rules are actually being appliedAffected if Custom firewall rules are configured but not appearing in the active ruleset
You are affected if OS X Server version is 4.0 or earlier AND custom firewall rules are configured but failing to load due to incorrect configuration file paths.
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 OS X Server to version 4.1 or later, which corrects the pathname in the firewall configuration. After upgrading, verify custom firewall rules are loading and applying correctly.
- Consultation3.0 h
- Implementation3.0 h
- Testing2.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 $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1150 — 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-2015-1150 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