Anyconnect Secure Mobility ClientApplication · Cisco
CVE-2017-12268
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 · uneditedA vulnerability in the Network Access Manager (NAM) of Cisco AnyConnect Secure Mobility Client could allow an authenticated, local attacker to enable multiple network adapters, aka a Dual-Homed Interface vulnerability. The vulnerability is due to insufficient NAM policy enforcement. An attacker could exploit this vulnerability by manipulating network interfaces of the device to allow multiple active network interfaces. A successful exploit could allow the attacker to send traffic over a non-authorized network interface. Cisco Bug IDs: CSCvf66539.
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 confidenceThis vulnerability in Cisco AnyConnect's Network Access Manager (NAM) allows a local authenticated attacker to enable multiple network adapters (dual-homing) due to insufficient policy enforcement. The attacker can manipulate network interfaces to have multiple active connections, enabling traffic to be sent over non-authorized network interfaces outside the controlled security policy.
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
Anyconnect Secure Mobility ClientApplication
= 4.5\(822\)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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/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.
-
Check the installed version of Cisco AnyConnect Secure Mobility ClientOpen the Windows Control Panel, go to Programs and Features, and look for Cisco AnyConnect Secure Mobility Client in the list of installed programs. Note the version number displayed.Affected if The installed version is exactly 4.5(822)
-
Verify the Network Access Manager (NAM) module is installedOpen Windows Services and look for a service named 'Cisco AnyConnect NAM' or check the Cisco AnyConnect installation directory for NAM-related DLL files or executables.Affected if NAM is installed and the version matches 4.5(822)
-
Check if multiple network adapters are simultaneously activeOpen Network and Sharing Center in Windows, click on Change adapter settings, and observe whether more than one adapter shows as Enabled and Connected.Affected if Multiple network adapters are active at the same time while NAM is running
-
Inspect the NAM policy configuration for dual-homing restrictionsOpen the Cisco AnyConnect client, navigate to the Network Access Manager settings, and review the policy configuration to see if restrictions on multiple network interfaces are defined or enforced.Affected if The policy allows multiple active adapters or lacks enforcement of single-homing restrictions
A system is affected if Cisco AnyConnect Secure Mobility Client version 4.5(822) with Network Access Manager is installed and the NAM policy does not prevent multiple simultaneous active network adapters.
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 this vulnerability (refer to CSCvf66539) to ensure NAM properly enforces policy restrictions preventing multiple active network adapters. Ensure anyConnect clients are updated to patched versions.
Fix this in Anyconnect Secure Mobility Client
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12268 — 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-2017-12268 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