CVE-2019-18181
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 · uneditedIn CloudVision Portal all releases in the 2018.1 and 2018.2 Code train allows users with read-only permissions to bypass permissions for restricted functionality via CVP API calls through the Configlet Builder modules. This vulnerability can potentially enable authenticated users with read-only access to take actions that are otherwise restricted in the GUI.
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 confidenceCloudVision Portal 2018.1 and 2018.2 releases contain an authorization bypass where users with read-only permissions can bypass GUI-enforced role restrictions by making direct API calls through Configlet Builder modules, enabling unauthorized configuration changes.
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>= 2018.1.0, <= 2018.1.4>= 2018.2.0, <= 2018.2.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 installed CloudVision Portal versionAccess the CloudVision Portal About or System Information page, or use the CLI command 'show version' on the CVP cluster to retrieve the running version numberAffected if The version falls within 2018.1.0-2018.1.4 or 2018.2.0-2018.2.3
-
Confirm Configlet Builder module is in useCheck if Configlet Builder functionality is accessible or enabled within the CloudVision Portal GUI under the Configlet or Builder sectionsAffected if Configlet Builder is accessible and active in the environment
-
Verify read-only user permissions at API levelUsing a read-only user account, attempt a direct API call to Configlet Builder endpoints (such as /api/v1/configlets or /api/v2/configlets) and observe whether the request is rejectedAffected if Read-only users can successfully execute API calls that modify configuration through Configlet Builder endpoints
-
Review user role assignmentsExamine the role assignments for read-only users in CloudVision Portal under Users > Roles to confirm which roles are assignedAffected if Read-only roles are assigned and Configlet Builder API endpoints are not blocked for these roles
A user is affected if their CloudVision Portal version is within the 2018.1.0-2018.1.4 or 2018.2.0-2018.2.3 range AND read-only users can successfully make configuration changes via Configlet Builder API endpoints.
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 CloudVision Portal to version 2019.x or later where the permission bypass is patched, or implement API access controls to enforce role-based restrictions at the API layer.
- Consultation3.0 h
- Implementation12.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 $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18181 — 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-18181 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