Network Admission ControlApplication · Cisco
CVE-2013-1124
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 Cisco Network Admission Control (NAC) agent on Mac OS X does not verify the X.509 certificate of an Identity Services Engine (ISE) server during an SSL session, which allows man-in-the-middle attackers to spoof ISE servers via an arbitrary certificate, aka Bug ID CSCub24309.
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 Cisco Network Admission Control (NAC) agent on Mac OS X fails to verify the X.509 certificate of Identity Services Engine (ISE) servers during SSL sessions. This allows man-in-the-middle attackers to spoof ISE servers using arbitrary certificates, enabling traffic interception and credential theft.
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
Network Admission ControlApplication
all 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/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.
-
Verify Cisco NAC agent is installed on Mac OS XCheck for the Cisco NAC agent by examining running processes: open Terminal and run 'ps -ef | grep -i nac' or look in /Applications for Cisco NAC-related applications. Also check System Preferences > Extensions or system daemons for NAC components.Affected if The Cisco NAC agent daemon or application is found running on Mac OS X
-
Confirm the NAC agent connects to ISE serversExamine NAC agent configuration files in /Library/Application Support/Cisco or /etc/cisco directories. Check for ISE server profiles or certificates configured for NAC SSL connections.Affected if NAC agent is configured to connect to Identity Services Engine servers via SSL
-
Verify SSL certificate validation behaviorUse network capture (tcpdump or Wireshark) to inspect SSL/TLS traffic between the NAC agent and ISE servers. Observe whether certificate chain validation occurs or if any certificate is accepted without verification.Affected if The NAC agent accepts SSL connections to ISE servers without validating the server X.509 certificate chain (certificate validation is bypassed)
If the Cisco NAC agent is installed and active on Mac OS X with ISE server connections, the environment is affected because all versions of the NAC agent fail to validate X.509 certificates during SSL sessions.
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 dataApply the Cisco patch for Bug ID CSCub24309 when available. Until then, consider network segmentation to isolate NAC infrastructure and monitor for suspicious SSL/TLS activity.
Fix this in Network Admission Control
Scoped from the published advisory
- 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-2013-1124 — 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-2013-1124 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