Meeting ServerApplication · Cisco
CVE-2019-1623
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 configuration shell of Cisco Meeting Server could allow an authenticated, local attacker to inject arbitrary commands as the root user. The vulnerability is due to insufficient input validation during the execution of a vulnerable CLI command. An attacker with administrator-level credentials could exploit this vulnerability by injecting crafted arguments during command execution. A successful exploit could allow the attacker to perform arbitrary code execution as root on an affected product.
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 command injection vulnerability in the CLI configuration shell of Cisco Meeting Server allows authenticated local attackers with administrator credentials to inject and execute arbitrary commands as root due to insufficient input validation during CLI command execution.
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
Meeting ServerApplication
>= 2.2.0, < 2.2.14>= 2.3.0, < 2.3.8CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Check Cisco Meeting Server version via CLILog into the Cisco Meeting Server CLI and run the command: 'version' or 'show version' to retrieve the installed software version.Affected if The displayed version falls within the vulnerable ranges: 2.2.0 through 2.2.13, or 2.3.0 through 2.3.7.
-
Verify CLI administrative access is enabledFrom the CLI, check if the configuration shell is accessible by attempting to enter configuration mode with the command 'configure' while logged in as an administrator.Affected if Administrative CLI access is enabled and the user has valid administrator credentials.
-
Confirm the system accepts CLI commandsExecute a safe read-only CLI command such as 'show status' or 'show call detail' to verify the CLI interface is functional and accepting input.Affected if CLI commands execute successfully, indicating the configuration shell is operational.
The environment is affected if the installed Cisco Meeting Server version is 2.2.0 through 2.2.13 or 2.3.0 through 2.3.7, and administrative CLI access is available and functional.
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 data2.2.142.3.8
Apply the Cisco vendor patch for CVE-2019-1623 and restrict administrative CLI access to trusted, vetted personnel to reduce the attack surface.
Fix this in Meeting Server
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing2.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 $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1623 — 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-1623 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