CVE-2005-4815

What it is

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."

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

2.6% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2005-12-31 05:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:19 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.6% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2005-12-31 05:00 UTC

Last modified

2026-06-16 22:19 UTC

Exploit probability

2.6% · EPSS, next 30 days

Record status

Modified

Affected

• Sap R 3 4.6_before_patch_1767
• Sap R 3 6.2_before_patch_1364
• Sap R 3 6.4_before_patch_4
• Sap R 3 31_before_31i_patch_735
• Sap R 3 40_before_patch_1008
• Sap R 3 45_before_patch_913

Attack profile CVSS 2.0 · 7.5

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

Partial

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2005-4815.md and follow it. Check whether this project is affected by CVE-2005-4815. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge