# CVE-2019-5619: AASync.com AASync Stack-based Buffer Overflow

> A stack-based buffer overflow in AASync allows attackers to execute arbitrary code via crafted input.

- **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:** 29 Apr 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vp54-8459-j943

## What is CVE-2019-5619?

CVE-2019-5619 is a critical memory corruption vulnerability in AASync.com AASync, published on 29 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Aasync Aasync.

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

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

## Is CVE-2019-5619 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-5619 exists.

Public exploit code:

- AASync v2.2.1.0 (Win32) Stack Buffer Overflow (LIST) (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5619 is a critical memory corruption vulnerability in AASync.com AASync, published on 29 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-5619 exists.

Affected product: AASync.com AASync. 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-5619/ (Markdown: https://insights.sbomify.com/CVE-2019-5619/index.md)
```

## Sources

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

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