Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-37373: Improper input validation in the Central Filestore in Ivanti Avalanche 6.3.1 allows a remote authenticated att

44
This month
HIGH 7.2DOWNGRADEDOWNGRADE

CVE-2024-37373 is a high-severity flaw (CVSS 7.2) affecting avalanche, avalanche. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Improper input validation in the Central Filestore in Ivanti Avalanche 6.3.1 allows a remote authenticated attacker with admin rights to achieve RCE.

Why this priority

  • High severity

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

Risk facts

CVSS score7.2 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance1.6% (top 25%)
CISA exploited listNo
WeaknessCWE-20
Published2024-08-14
Last modified2026-06-17
Publisher (CNA): HackerOne · Vendor: ivanti

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

ivanti avalanche DOWNGRADE
Affected: 6.3.1 · 6.3.1.1507 · 6.3.2 · 6.3.2.3490 · 6.3.3 · 6.3.3.101 · 6.3.4 · 6.3.4.153
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.3.1
1. Check installed version
apt-cache policy avalanche || rpm -q avalanche || avalanche --version
2. No fixed release: DOWNGRADE to a release before 6.3.1 (Debian / Ubuntu)
apt-cache madison avalanche sudo apt install avalanche=<VERSION_BEFORE_6.3.1> sudo apt-mark hold avalanche
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list avalanche sudo dnf downgrade avalanche-<VERSION_BEFORE_6.3.1> sudo dnf versionlock add avalanche
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.
ivanti avalanche DOWNGRADE
Affected: 6.3.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.3.2
1. Check installed version
apt-cache policy avalanche || rpm -q avalanche || avalanche --version
2. No fixed release: DOWNGRADE to a release before 6.3.2 (Debian / Ubuntu)
apt-cache madison avalanche sudo apt install avalanche=<VERSION_BEFORE_6.3.2> sudo apt-mark hold avalanche
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list avalanche sudo dnf downgrade avalanche-<VERSION_BEFORE_6.3.2> sudo dnf versionlock add avalanche
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.
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-2024-37373?

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

Is CVE-2024-37373 being exploited?

CVE-2024-37373 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-2024-37373 affect?

CVE-2024-37373 affects avalanche, avalanche. Severity is high (CVSS 7.2). Improper input validation in the Central Filestore in Ivanti Avalanche 6.3.1 allows a remote authenticated attacker with admin rights to achieve RCE.

How urgent is CVE-2024-37373?

Priority 44/100. High severity

Software pages

Ivanti vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.