# CVE-2022-20814: Cisco Expressway Series and Cisco TelePresence VCS Improper Certificate Validation Vulnerability > An unauthenticated remote attacker can intercept and alter traffic between Cisco Expressway-C and Unified Communications Manager via a man-in-the-middle attack due to improper certificate validation. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 15 Nov 2024 - **Updated:** 15 Nov 2024 - **Also known as:** GHSA-rg5m-fc62-h68h ## What is CVE-2022-20814? CVE-2022-20814 is a high-severity vulnerability in Cisco TelePresence Video Communication Server (VCS) Expressway, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in the certificate validation of Cisco Expressway-C and Cisco TelePresence VCS could allow an unauthenticated, remote attacker to gain unauthorized access to sensitive data.  The vulnerability is due to a lack of validation of the SSL server certificate that an affected device receives when it establishes a connection to a Cisco Unified Communications Manager device. An attacker could exploit this vulnerability by using a man-in-the-middle technique to intercept the traffic between the devices, and then using a self-signed certificate to impersonate the endpoint. A successful exploit could allow the attacker to view the intercepted traffic in clear text or alter the contents of the traffic. Note: Cisco Expressway-E is not affected by this vulnerability.Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. Weakness: CWE-295 (Improper Certificate Validation) ## Which versions are affected by CVE-2022-20814? It affects 1 product. Products: Cisco Telepresence Video Communication Server. ## How do I fix CVE-2022-20814? No fix has been published for CVE-2022-20814 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-20814 being exploited? There is no known exploitation of CVE-2022-20814 in the wild and no public exploit code. ## Other vulnerabilities in Cisco TelePresence Video Communication Server (VCS) Expressway - [CVE-2023-20105](https://insights.sbomify.com/CVE-2023-20105/): Privilege escalation in Cisco TelePresence Video Communication Server (VCS) Expressway (critical 9.6) - [CVE-2023-20192](https://insights.sbomify.com/CVE-2023-20192/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Privilege Escalation Vulnerabilities (critical 9.6) - [CVE-2022-20754](https://insights.sbomify.com/CVE-2022-20754/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0) - [CVE-2022-20755](https://insights.sbomify.com/CVE-2022-20755/): Cisco Expressway Series and Cisco TelePresence Video Communication Server Vulnerabilities (critical 9.0) - [CVE-2016-1468](https://insights.sbomify.com/CVE-2016-1468/): Command injection in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-20814 and fix it if it is affected. What it is: CVE-2022-20814 is a high-severity vulnerability in Cisco TelePresence Video Communication Server (VCS) Expressway, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-20814 in the wild and no public exploit code. Affected product: Cisco TelePresence Video Communication Server (VCS) Expressway. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-20814/ (Markdown: https://insights.sbomify.com/CVE-2022-20814/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-20814 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-20814 - OSV: https://osv.dev/vulnerability/CVE-2022-20814 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-20814/ Summaries are generated and may contain mistakes; the official description above is the record.