cve.bz

CVE-2005-4815 sap sap r 3

no score yetEPSS 2.6%

sap sap r 3: no CVSS score yet. EPSS 2.6% estimated probability of exploitation activity in the next 30 days.

SAP 6.4 before 6.40 patch 4, 6.2 before 6.20 patch 1364, 4.6 before 4.6D patch 1767, 45 before 45B patch 913, 40 before 40B patch 1008, and 31 before 31I patch 735 do not properly restrict process execution by lnaxdm/sapsys, which allows remote attackers to execute arbitrary code via a certain UDP packet that ends with the name of a local executable file, aka the "FX SAP R/3 gwrd vuln."
EPSS
2.6% (unchanged from 2.6% a week ago; 2.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 86th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2005-4815 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2005-4815?via=ask-ai-copy and https://cve.bz/cve/CVE-2005-4815?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-2005-4815 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
sap:sap_r_34.6_before_patch_1767
sap:sap_r_36.2_before_patch_1364
sap:sap_r_36.4_before_patch_4
sap:sap_r_331_before_31i_patch_735
sap:sap_r_340_before_patch_1008
sap:sap_r_345_before_patch_913

References

Check your stackJSON