CVE-2019-5619
AASync.com AASync Stack-based Buffer Overflow
AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
9.8
AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.
- Record
CVE-2019-5619- CVSS 3.1
- 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-121, CWE-787
- Updated
- 2026-11-02
CVE List No score
AASync.com AASync Stack-based Buffer Overflow
AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.
- Record
CVE-2019-5619- Weakness
- CWE-121
- Updated
- 2026-11-02
EUVDEUVD-2019-15194 No score
AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.
- Record
EUVD-2019-15194- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-vp54-8459-j943 No score
AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.
AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.
- Record
GHSA-vp54-8459-j943- Weakness
- CWE-787
- Updated
- 2026-11-02
Affected products
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Metasploit | AASync v2.2.1.0 (Win32) Stack Buffer Overflow (LIST) | 2010-10-12 |
History
| Recorded | Changed | Sources |
|---|---|---|
| facts | ||
| aliases, published | EUVD | |
| first indexed | CVE List, GitHub Advisories, Metasploit, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2019-5619 is a critical vulnerability (CVSS 9.8) in Aasync, published April 29, 2020. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 4.72%, the 91st percentile. No source names a fixed version.