CVE-2017-12214
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 Operations, Administration, Maintenance, and Provisioning (OAMP) credential reset functionality for Cisco Unified Customer Voice Portal (CVP) could allow an authenticated, remote attacker to gain elevated privileges. The vulnerability is due to a lack of proper input validation. An attacker could exploit this vulnerability by authenticating to the OAMP and sending a crafted HTTP request. A successful exploit could allow the attacker to gain administrator privileges. The attacker must successfully authenticate to the system to exploit this vulnerability. This vulnerability affects Cisco Unified Customer Voice Portal (CVP) running software release 10.5, 11.0, or 11.5. Cisco Bug IDs: CSCve92752.
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 confidenceA privilege escalation vulnerability in the OAMP (Operations, Administration, Maintenance, and Provisioning) component of Cisco Unified Customer Voice Portal allows authenticated remote attackers to gain administrator privileges by sending a crafted HTTP request. The vulnerability stems from insufficient input validation in the credential reset functionality.
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.5= 11.0= 11.5CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Cisco Unified Customer Voice Portal installationLocate the CVP installation directory or check system inventory for 'Cisco Unified Customer Voice Portal' or 'CVP' software componentAffected if The product is not Cisco Unified Customer Voice Portal, then not affected by this CVE
-
Verify installed CVP versionCheck the installed CVP version using the CVP Administration interface (OAMP > System > CVP Server) or via command line: cvp_version.bat or equivalent version check utilityAffected if The installed version is exactly 10.5, 11.0, or 11.5 - these are the affected versions listed
-
Confirm OAMP component is accessibleAccess the OAMP web interface by navigating to https://<cvp-server>/oamp and verify the Operations, Administration, Maintenance, and Provisioning portal is reachableAffected if OAMP interface is not accessible (not installed or not running), the exploit vector may not be available
-
Check OAMP remote access configurationReview OAMP security settings in the administration console under 'System > Security' or check if the OAMP listener is bound to externally accessible network interfaces (not just localhost/internal VLAN)Affected if OAMP is exposed to untrusted networks or remote access is enabled, authenticated attackers could reach the vulnerable credential reset function
A user is affected if they have Cisco Unified Customer Voice Portal versions 10.5, 11.0, or 11.5 running with the OAMP component accessible to authenticated remote 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 dataApply the Cisco patch for the affected versions (10.5, 11.0, 11.5) when available, and restrict OAMP interface access to trusted administrators only through network segmentation or VPN access controls.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12214 — 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-12214 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