# CVE-2019-20502: Memory corruption in n/a

> A buffer overflow in EFS Easy Chat Server allows attackers to execute arbitrary code or cause a denial of service via a long message parameter.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 5 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qj55-crj2-57h4

## What is CVE-2019-20502?

CVE-2019-20502 is a high-severity memory corruption vulnerability in n/a, published on 5 Mar 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 EFS Easy Chat Server 3.1. There is a buffer overflow via a long body2.ghp message parameter.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2019-20502?

It affects 1 product.


Products: Echatserver Easy Chat Server.

## How do I fix CVE-2019-20502?

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

## Is CVE-2019-20502 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9544](https://insights.sbomify.com/CVE-2017-9544/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-25221](https://insights.sbomify.com/CVE-2018-25221/): EChat Server 3.1 Buffer Overflow via chat.ghp username Parameter (critical 9.3)
- [CVE-2019-25613](https://insights.sbomify.com/CVE-2019-25613/): Easy Chat Server 3.1 Denial of Service via message Parameter (high 8.7)
- [CVE-2022-44939](https://insights.sbomify.com/CVE-2022-44939/): Other in n/a (high 7.8)
- [CVE-2017-9543](https://insights.sbomify.com/CVE-2017-9543/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-20502 and fix it if it is affected.

What it is: CVE-2019-20502 is a high-severity memory corruption vulnerability in n/a, published on 5 Mar 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-2019-20502 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-2019-20502/ (Markdown: https://insights.sbomify.com/CVE-2019-20502/index.md)
```

## Sources

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

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