Hosted Collaboration SolutionApplication · Cisco
CVE-2019-1911
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 CLI of Cisco Unified Communications Domain Manager (Cisco Unified CDM) Software could allow an authenticated, local attacker to escape the restricted shell. The vulnerability is due to insufficient input validation of shell commands. An attacker could exploit this vulnerability by executing crafted commands in the shell. A successful exploit could allow the attacker to escape the restricted shell and access commands in the context of the restricted shell user, which does not have root 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 confidenceA CLI command injection vulnerability in Cisco Unified CDM allows an authenticated local attacker to escape the restricted shell by executing crafted commands. The vulnerability stems from insufficient input validation in the CLI, enabling the attacker to break out of the restricted shell and execute commands in the context of the non-root restricted user.
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
Hosted Collaboration SolutionApplication
<= 11.5\(3\)pb3CVSS 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.0/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 the Cisco product and versionAccess the CLI or administrative interface and run the command to display the version (typically 'show version' or check the About section in the management GUI). Look for the exact version string such as 11.5(x) or 11.5(3)pb3.Affected if The installed product is Cisco Unified CDM or Cisco Hosted Collaboration Solution and the version is 11.5(3)pb3 or any earlier version (e.g., 11.5, 11.5(1), 11.5(2), 11.5(3)).
-
Confirm CLI access is enabledCheck if the command-line interface is accessible via SSH, console, or admin portal. Verify that local authentication is configured and the restricted shell environment exists.Affected if CLI access is available and the attacker can authenticate as a local restricted user.
-
Review system logs for shell escape attemptsExamine CLI command logs, system logs, and audit logs for patterns indicating attempts to break out of the restricted shell (e.g., unusual command sequences, semicolon or pipe operators followed by system commands, environment variable injections).Affected if Log entries show unauthorized command execution attempts or evidence of restricted shell bypass.
-
Check for unauthorized user accountsReview the list of local user accounts configured on the system and verify that only expected authorized users exist with CLI access.Affected if Unexpected local accounts are present or accounts other than designated administrators have CLI access.
A system is affected if it runs Cisco Unified CDM or Cisco Hosted Collaboration Solution version 11.5(3)pb3 or earlier and has CLI access available to authenticated local 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 Cisco patches when available; until then, limit local authenticated access to trusted personnel only and monitor for unauthorized shell escape attempts.
Fix this in Hosted Collaboration Solution
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1911 — 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-1911 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