# CVE-2022-29820: In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible


- **Severity:** Low 3.0 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-vvwg-mm2q-wvgr

## What is CVE-2022-29820?

CVE-2022-29820 is a low-severity vulnerability in JetBrains PyCharm, published on 28 Apr 2022. 

### Official description

In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-1327 (Binding to an Unrestricted IP Address)

## Which versions are affected by CVE-2022-29820?

It affects 1 product.


Products: Jetbrains Pycharm.

## How do I fix CVE-2022-29820?

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

## Is CVE-2022-29820 being exploited?

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

## Other vulnerabilities in JetBrains PyCharm

- [CVE-2026-65908](https://insights.sbomify.com/CVE-2026-65908/): Code injection in PyCharm (high 8.6)
- [CVE-2026-75060](https://insights.sbomify.com/CVE-2026-75060/): Missing authorization in PyCharm (high 8.4)
- [CVE-2026-25847](https://insights.sbomify.com/CVE-2026-25847/): Cross-site scripting in PyCharm (high 8.2)
- [CVE-2021-30005](https://insights.sbomify.com/CVE-2021-30005/): Code injection in n/a (high 7.8)
- [CVE-2020-11694](https://insights.sbomify.com/CVE-2020-11694/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29820 and fix it if it is affected.

What it is: CVE-2022-29820 is a low-severity vulnerability in JetBrains PyCharm, published on 28 Apr 2022. 
Exploitation: There is no known exploitation of CVE-2022-29820 in the wild and no public exploit code.

Affected product: JetBrains PyCharm. 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-29820/ (Markdown: https://insights.sbomify.com/CVE-2022-29820/index.md)
```

## Sources

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

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