Prime InfrastructureApplication · Cisco
CVE-2019-1906
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 Virtual Domain system of Cisco Prime Infrastructure (PI) could allow an authenticated, remote attacker to change the virtual domain configuration, which could lead to privilege escalation. The vulnerability is due to improper validation of API requests. An attacker could exploit this vulnerability by manipulating requests sent to an affected PI server. A successful exploit could allow the attacker to change the virtual domain configuration and possibly elevate privileges.
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 confidenceVulnerability in Cisco Prime Infrastructure Virtual Domain system allows authenticated remote attackers to manipulate API requests to change virtual domain configuration, potentially escalating privileges due to improper validation of incoming API requests.
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
Prime InfrastructureApplication
= 3.6CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Identify Cisco Prime Infrastructure versionAccess the Prime Infrastructure admin console or use the CLI command 'show version' to determine the installed software versionAffected if The installed version is exactly 3.6 (CPE version 3.6.x)
-
Verify Virtual Domain feature is enabledCheck the Prime Infrastructure configuration for Virtual Domain settings - typically found in the administration or system settings area of the web UI, or via CLI command 'show virtual-domain status' if availableAffected if Virtual Domain feature is enabled and configured with multiple virtual domains
-
Confirm API access is configuredReview the Prime Infrastructure API settings in the administration menu to determine if REST API or other programmatic interfaces are enabledAffected if API access is permitted for authenticated users
-
Inspect virtual domain configuration permissionsExamine the virtual domain configuration settings and user role assignments to identify if low-privilege authenticated users can access virtual domain management APIsAffected if Authenticated users with limited roles can modify virtual domain configurations via API calls
-
Review API request loggingCheck Prime Infrastructure logs (typically in /opt/CSPrimeLabs/ or similar logs directory) for API requests targeting virtual domain endpoints, looking for unexpected or unauthorized configuration changesAffected if API activity logs show virtual domain configuration changes from users who should not have such permissions
A user is affected if they are running exactly Cisco Prime Infrastructure version 3.6 with Virtual Domain and API access both enabled, allowing authenticated users to manipulate virtual domain configurations beyond their intended privileges.
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 Cisco security patches for CVE-2019-1906 when available; restrict API access to trusted authenticated users and implement monitoring for unauthorized virtual domain configuration changes.
Fix this in Prime Infrastructure
Scoped from the published advisory
- Consultation6.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1906 — 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-2019-1906 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