dbcve.org
Rfc LibraryApplication · Sap

CVE-2007-1916

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 RFC_START_GUI 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 vulnerability in the RFC_START_GUI function of 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 SAP's RFC communication library that could allow complete system compromise.

MitigationUpdate SAP RFC Library to version 7.00 build date 20061211 or later to patch the buffer overflow in the RFC_START_GUI function. Apply the available vendor patch immediately given the CVSS 10 severity.

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. Locate the SAP RFC Library files
    Search for librfc32.dll (Windows) or libsaprfc* (Unix) in the SAP installation directory, system32/sysWOW64, or application bin folders. Common paths: C:\Windows\System32\librfc32.dll or /usr/sap/*/SYS/exe/run/
    Affected if The SAP RFC Library file exists on the system, indicating SAP RFC functionality is installed
  2. Retrieve the library file version
    Right-click the librfc32.dll file, select Properties, then view the Version tab. Alternatively, use a command: on Windows use 'dir /-c' for timestamps or a tool like 'exiftool' or 'strings' to extract version metadata. Check the File Version field specifically.
    Affected if The file version shows 6.40.x.x or 7.00.x.x, indicating a vulnerable version
  3. Identify the build date for version 7.00
    In the file Properties under Version tab, check the 'Product Version' field or 'Build' field. The build date format is YYYYMMDD. For version 7.00, compare the build date to 20061211.
    Affected if Product version is 7.00 with a build date earlier than 20061211 (for example, 20061015) - this indicates the unpatched vulnerable version
  4. Confirm version 6.40 is affected
    If the version field shows 6.40.x.x (any patch level), note that all versions 6.40 are affected per the CVE.
    Affected if The library version is exactly 6.40 or 6.4 (any subversion) - these are all vulnerable regardless of build date
  5. Check if RFC_START_GUI is invoked
    Review application logs, SAP configuration files (saprfc.ini), or ABAP reports that may call the RFC_START_GUI function. This function is used to launch SAP GUI from RFC calls.
    Affected if The system uses RFC_START_GUI functionality in any SAP communication, which exposes the buffer overflow attack surface

The system is affected if SAP RFC Library version 6.40 (any build) or version 7.00 with build date before 20061211 is present and RFC communication is enabled.

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

Update SAP RFC Library to version 7.00 build date 20061211 or later to patch the buffer overflow in the RFC_START_GUI function. Apply the available vendor patch immediately given the CVSS 10 severity.

Fix this in Rfc Library Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1916 — 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-1916 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