dbcve.org
Sap R 3Application · Sap

CVE-2005-4815

HIGH · 7.5 CVSS v2.0 Published 2005-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SAP R/3 gateway process (gwrd) does not properly restrict process execution by the lnaxdm/sapsys component, allowing remote attackers to execute arbitrary code by sending specially crafted UDP packets containing the filename of a local executable.

MitigationApply the appropriate SAP security patch for your version (6.40 patch 4, 6.20 patch 1364, 4.6D patch 1767, 45B patch 913, 40B patch 1008, or 31I patch 735). Additionally, restrict network access to the SAP gateway UDP port (3300-3399 typically) to prevent unauthorized external packets.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sap R 3Application
Affected:= 4.6_before_patch_1767= 6.2_before_patch_1364= 6.4_before_patch_4= 31_before_31i_patch_735= 40_before_patch_1008= 45_before_patch_913

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify SAP Gateway process is running
    Check for the gwrd process on the SAP system using process listing commands (e.g., ps -ef | grep gwrd or task manager on Windows). Also verify UDP ports 3300-3399 are in listening state.
    Affected if The gwrd process is running and UDP ports 3300-3399 are open and listening.
  2. Determine installed SAP R/3 version
    Use SAP transaction code SM51 to view the SAP Release version, or check the saposcol/log files for version information. Compare against: 4.6 before patch 1767, 6.2 before patch 1364, 6.4 before patch 4, 31i before patch 735, 40 before patch 1008, 45 before patch 913.
    Affected if The installed version matches one of the affected version ranges and is before the corresponding patch level.
  3. Check network exposure of UDP ports 3300-3399
    Use netstat -anup or similar network inspection tools to confirm UDP ports 3300-3399 are bound to accessible network interfaces. Verify whether these ports are reachable from untrusted networks.
    Affected if UDP ports 3300-3399 are accessible from external or untrusted network segments.
  4. Verify lnaxdm/sapsys component presence
    Inspect the SAP gateway configuration and the presence of the lnaxdm or sapsys executable components in the SAP system directories (typically under /sapmnt/<SID>/exe or the corresponding SAP global directory).
    Affected if The lnaxdm or sapsys component exists and is callable through the gateway.

The system is affected if the SAP gateway process is running, the installed version is one of the affected releases before the corresponding patch level, and UDP ports 3300-3399 are network-accessible to untrusted parties.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate SAP security patch for your version (6.40 patch 4, 6.20 patch 1364, 4.6D patch 1767, 45B patch 913, 40B patch 1008, or 31I patch 735). Additionally, restrict network access to the SAP gateway UDP port (3300-3399 typically) to prevent unauthorized external packets.

Fix this in Sap R 3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-4815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-4815 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data