dbcve.org
Rfc LibraryApplication · Sap

CVE-2007-1917

HIGH · 10.0 CVSS v2.0 Published 2007-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Buffer overflow in the SYSTEM_CREATE_INSTANCE function in the SAP RFC Library 6.40 and 7.00 before 20061211 allows remote attackers to execute arbitrary code via unspecified vectors. NOTE: This information is based upon a vague initial disclosure. Details will be updated after the grace period has ended.

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 · moderate confidence

Buffer overflow in the SYSTEM_CREATE_INSTANCE function in SAP RFC Library versions 6.40 and 7.00 (before 20061211) allows remote attackers to execute arbitrary code via unspecified vectors. This is a critical flaw in a core SAP communication library.

MitigationApply SAP security patch to update RFC Library to a version after 20061211, or upgrade to a supported SAP version. Implement network segmentation to restrict access to SAP RFC services from untrusted networks.

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
Rfc LibraryApplication
Affected:= 6.4= 7.0

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
Complete
Integrity
Complete
Availability
Complete

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

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. Identify the installed SAP RFC Library version
    Locate the SAP RFC Library files (typically sapnwrfc.dll on Windows or librfc.so on Unix) in the SAP system directories or application server path. Use file properties or version inquiry tools to read the version metadata embedded in the library binary.
    Affected if The version displayed is 6.40 or 7.00 and the release date shown is before December 11, 2006 (20061211).
  2. Confirm the exact RFC Library release date
    Check the SAP RFC Library patch level or build timestamp. This information may be available via SAP transaction code SM51 (for SAP kernel), in the SAP Note related to the library, or by examining version strings within the RFC DLL/SO file properties.
    Affected if The library build or patch date predates the 20061211 patch release.
  3. Determine if SYSTEM_CREATE_INSTANCE function is accessible
    Verify whether the SAP RFC service is exposed and accessible. Check if remote function call (RFC) connections are enabled and reachable over the network. Use SAP transaction SE37 to review the SYSTEM_CREATE_INSTANCE function module if accessible, or inspect RFC destination configurations (transaction SM59).
    Affected if The SYSTEM_CREATE_INSTANCE function is exposed and callable from remote network locations without authentication restrictions.
  4. Check network exposure of SAP RFC services
    Review firewall rules, SAP gateway configuration (transaction SAPG), and RFC destination settings (SM59) to determine if RFC communication ports (typically 33xx range) are reachable from untrusted networks or external IP addresses.
    Affected if SAP RFC services are listening on accessible network interfaces and allow connections from untrusted or external systems.

A user is affected if their SAP RFC Library version is 6.40 or 7.00 with a release date before December 11, 2006, and the SYSTEM_CREATE_INSTANCE function is network-accessible.

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 SAP security patch to update RFC Library to a version after 20061211, or upgrade to a supported SAP version. Implement network segmentation to restrict access to SAP RFC services from untrusted networks.

Fix this in Rfc Library 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-2007-1917 — 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-2007-1917 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