Skip to content
Fencer Intel
high 8.2

CVE-2024-21894 in the critical feed json

A heap overflow vulnerability in IPSec component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated ma…

published 2y ago modified 4mo ago also EUVD-2024-19505

cvss
8.2
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
19.0%
EPSS 19.0% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

A heap overflow vulnerability in IPSec component of Ivanti Connect Secure (9.x, 22.x) and Ivanti Policy Secure allows an unauthenticated malicious user to send specially crafted requests in-order-to crash the service thereby causing a DoS attack. In certain conditions this may lead to execution of arbitrary code

Is CVE-2024-21894 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

18.99% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.0 8.2 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Ivanti Connect Secure
  • Ivanti Policy Secure
  • ivanti connect_secure
  • ivanti policy_secure

Classification

Weakness
  • CWE-703 Improper Check or Handling of Exceptional Conditions
  • CWE-787 Out-of-bounds Write
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.