# CVE-2020-12338: Privilege escalation in Open WebRTC Toolkit

> An unauthenticated attacker can escalate privileges via network access due to insufficient control flow management in the Open WebRTC Toolkit.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-84r5-9fwf-5v5f

## What is CVE-2020-12338?

CVE-2020-12338 is a critical vulnerability in Open WebRTC Toolkit, published on 13 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficient control flow management in the Open WebRTC Toolkit before version 4.3.1 may allow an unauthenticated user to potentially enable escalation of privilege via network access.

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

It affects 1 product.


Products: Intel Open Webrtc Toolkit.

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

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

## Is CVE-2020-12338 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12338 is a critical vulnerability in Open WebRTC Toolkit, published on 13 Nov 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-12338 in the wild and no public exploit code.

Affected product: Open WebRTC Toolkit. 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-12338/ (Markdown: https://insights.sbomify.com/CVE-2020-12338/index.md)
```

## Sources

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

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