cve.bz

CVE-2025-0293 ivanti: CRLF Injection

2.7 lowEPSS 0.4%

Low (2.7) in ivanti. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
CLRF injection in Ivanti Connect Secure before version 22.7R2.8 and Ivanti Policy Secure before version 22.7R1.5 allows a remote authenticated attacker with admin rights to write to a protected configuration file on disk.

Severity

CVSS 3.1

2.7 low
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-07-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-93 Improper Neutralization of CRLF Sequences (CRLF Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-0293 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-0293?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-0293?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-0293 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_securebefore 22.7
ivanti:connect_secure22.7
ivanti:connect_secure22.7:r1
ivanti:connect_secure22.7:r1.1
ivanti:connect_secure22.7:r1.2
ivanti:connect_secure22.7:r1.3
ivanti:connect_secure22.7:r1.4
ivanti:connect_secure22.7:r1.5
ivanti:connect_secure22.7:r2
ivanti:connect_secure22.7:r2.1
ivanti:connect_secure22.7:r2.2
ivanti:connect_secure22.7:r2.3
ivanti:connect_secure22.7:r2.4
ivanti:connect_secure22.7:r2.5
ivanti:connect_secure22.7:r2.6
ivanti:connect_secure22.7:r2.7
ivanti:policy_securebefore 22.7
ivanti:policy_secure22.7
ivanti:policy_secure22.7:r1
ivanti:policy_secure22.7:r1.1
ivanti:policy_secure22.7:r1.2
ivanti:policy_secure22.7:r1.3
ivanti:policy_secure22.7:r1.4

Attack patterns (CAPEC)

  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON