# CVE-2021-34743: Cisco Webex Software Application Authorization Bypass Vulnerability

> An attacker can trick a user into authorizing a malicious application, allowing unauthorized access to the user's profile data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Oct 2021
- **Updated:** 7 Nov 2024
- **Also known as:** GHSA-xggx-cjmv-qpq3

## What is CVE-2021-34743?

CVE-2021-34743 is a medium-severity vulnerability in Cisco Webex Meetings, published on 21 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the application integration feature of Cisco Webex Software could allow an unauthenticated, remote attacker to authorize an external application to integrate with and access a user's account without that user's express consent. This vulnerability is due to improper validation of cross-site request forgery (CSRF) tokens. An attacker could exploit this vulnerability by convincing a targeted user who is currently authenticated to Cisco Webex Software to follow a link designed to pass malicious input to the Cisco Webex Software application authorization interface. A successful exploit could allow the attacker to cause Cisco Webex Software to authorize an application on the user's behalf without the express consent of the user, possibly allowing external applications to read data from that user's profile.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-34743?

It affects 1 product.


Products: Cisco Webex Meetings.

## How do I fix CVE-2021-34743?

No fix has been published for CVE-2021-34743 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-34743 being exploited?

There is no known exploitation of CVE-2021-34743 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Webex Meetings

- [CVE-2017-12368](https://insights.sbomify.com/CVE-2017-12368/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12369](https://insights.sbomify.com/CVE-2017-12369/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12370](https://insights.sbomify.com/CVE-2017-12370/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12371](https://insights.sbomify.com/CVE-2017-12371/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)
- [CVE-2017-12372](https://insights.sbomify.com/CVE-2017-12372/): Memory corruption in Cisco WebEx Recording Format and Advanced Recording Format Players (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34743 and fix it if it is affected.

What it is: CVE-2021-34743 is a medium-severity vulnerability in Cisco Webex Meetings, published on 21 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-34743 in the wild and no public exploit code.

Affected product: Cisco Webex Meetings. 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-2021-34743/ (Markdown: https://insights.sbomify.com/CVE-2021-34743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-34743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-34743
- OSV: https://osv.dev/vulnerability/CVE-2021-34743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-34743/
Summaries are generated and may contain mistakes; the official description above is the record.