CVE-2016-9012
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 · uneditedCloudVision Portal (CVP) before 2016.1.2.1 allows remote authenticated users to gain access to the internal configuration mechanisms via the management plane, related to a request to /web/system/console/bundle.
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 confidenceArista CloudVision Portal (CVP) before version 2016.1.2.1 exposes the Apache Felix Web Console endpoint at /web/system/console/bundle to remote authenticated users. This allows authenticated attackers to access internal OSGi configuration mechanisms and potentially modify system settings via the management plane.
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<= 2016.1.2.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
- 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 the installed CVP versionAccess the CVP web interface and navigate to the About section, or use the CVP CLI command 'show version' from the CVP console to retrieve the current software version.Affected if The installed version is 2016.1.2.0 or earlier.
-
Confirm the Felix Web Console endpoint is accessibleUsing a web browser or HTTP client, attempt to access the URL path /web/system/console/bundle on the CVP management interface. This may require prior authentication to CVP.Affected if The page loads and displays OSGi bundle information or the Apache Felix Web Console interface without additional authentication beyond CVP login.
-
Verify the endpoint responds to authenticated requestsLog into CVP with a valid user account, then navigate to or request the /web/system/console/bundle endpoint while authenticated.Affected if The Felix Web Console becomes accessible after standard CVP authentication, indicating the vulnerability is present.
-
Check if the /web/system/console/bundle endpoint is reachable from untrusted networksAttempt to access the endpoint from a non-management network segment or external IP address if CVP is exposed to such networks.Affected if The endpoint is reachable from network segments that should not have management plane access.
If the CVP version is 2016.1.2.0 or earlier AND the /web/system/console/bundle endpoint is accessible to authenticated users, the environment is affected by this CVE.
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 CVP to version 2016.1.2.1 or later. Alternatively, restrict network access to the management interface and disable or protect the Felix Web Console endpoint with additional authentication controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-9012 — 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-2016-9012 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