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

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2019-5619 is a critical-severity flaw (CVSS 9.8) affecting aasync. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Critical severity
EPSS top 8%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	4.7% (top 8%)
CISA exploited list	No
Weakness	CWE-121, CWE-787
Published	2020-04-29
Last modified	2026-06-17

Publisher (CNA): Rapid7, Inc. · Vendor: aasync

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-04-29 23:15 UTCPublished CVE record published
2026-06-17 02:37 UTCUpdated Record last modified

aasync aasync DOWNGRADE

Affected: 2.2.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.2.1.0

1. Check installed version

apt-cache policy aasync || rpm -q aasync || aasync --version

2. No fixed release: DOWNGRADE to a release before 2.2.1.0 (Debian / Ubuntu)

apt-cache madison aasync sudo apt install aasync=<VERSION_BEFORE_2.2.1.0> sudo apt-mark hold aasync

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list aasync sudo dnf downgrade aasync-<VERSION_BEFORE_2.2.1.0> sudo dnf versionlock add aasync

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Metasploit: AASync v2.2.1.0 (Win32) Stack Buffer Overflow (LIST)

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-5619?

aasync: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-5619 being exploited?

CVE-2019-5619 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-5619 affect?

CVE-2019-5619 affects aasync. Severity is critical (CVSS 9.8). AASync.com AASync version 2.2.1.0 suffers from an instance of CWE-121: Stack-based Buffer Overflow.

How urgent is CVE-2019-5619?

Priority 67/100. Critical severity; EPSS top 8%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs