# CVE-2020-13899: Information disclosure in n/a

> An attacker can read uninitialized stack memory via incoming requests, potentially exposing sensitive data from the Janus WebRTC Server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** Yes
- **Published:** 10 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-13899, GHSA-x6c3-mvjq-f4mg, UBUNTU-CVE-2020-13899

## What is CVE-2020-13899?

CVE-2020-13899 is a high-severity vulnerability in n/a, published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in janus-gateway (aka Janus WebRTC Server) through 0.10.0. janus_process_incoming_request in janus.c discloses information from uninitialized stack memory.

Weakness: CWE-908 (Use of Uninitialized Resource)

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

It affects 1 product.


Products: Meetecho Janus.

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

Upgrade to a fixed version.

## Is CVE-2020-13899 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-14033](https://insights.sbomify.com/CVE-2020-14033/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-14034](https://insights.sbomify.com/CVE-2020-14034/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-13901](https://insights.sbomify.com/CVE-2020-13901/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-10574](https://insights.sbomify.com/CVE-2020-10574/): Null dereference in n/a (critical 9.8)
- [CVE-2021-4020](https://insights.sbomify.com/CVE-2021-4020/): Cross-site Scripting (XSS) - Stored in meetecho/janus-gateway (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13899 is a high-severity vulnerability in n/a, published on 10 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-13899 in the wild and no public exploit code.

Affected product: n/a. 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-13899/ (Markdown: https://insights.sbomify.com/CVE-2020-13899/index.md)
```

## Sources

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

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