# CVE-2020-1343: Information disclosure in Microsoft Visual Studio Code Live Share extension

> Attackers can read sensitive tokens exposed in plain text by the Visual Studio Code Live Share extension, potentially compromising user sessions.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 9 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3cpw-x2mc-w7ch

## What is CVE-2020-1343?

CVE-2020-1343 is a medium-severity vulnerability in Microsoft Visual Studio Code Live Share extension, published on 9 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability exists in Visual Studio Code Live Share Extension when it exposes tokens in plain text, aka 'Visual Studio Code Live Share Information Disclosure Vulnerability'.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2020-1343?

It affects 1 product.


Products: Microsoft Visual Studio Live Share.

## How do I fix CVE-2020-1343?

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

## Is CVE-2020-1343 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1343 and fix it if it is affected.

What it is: CVE-2020-1343 is a medium-severity vulnerability in Microsoft Visual Studio Code Live Share extension, published on 9 Jun 2020. 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-2020-1343 in the wild and no public exploit code.

Affected product: Microsoft Visual Studio Code Live Share extension. 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-2020-1343/ (Markdown: https://insights.sbomify.com/CVE-2020-1343/index.md)
```

## Sources

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

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