CVE-2007-1915
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 · uneditedBuffer overflow in the RFC_START_PROGRAM 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 confidenceBuffer overflow vulnerability in the RFC_START_PROGRAM function of SAP RFC Library versions 6.40 and 7.00 (before 20061211) allows remote attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from improper bounds checking in the RFC_START_PROGRAM function which handles program execution calls over SAP's RFC protocol.
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= 6.4= 7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate SAP RFC Library installationSearch for librfc.dll, librfc.so, or sapnwrfc.dll files on the system. Common locations include system directories, SAP client installations, or custom application folders.Affected if The SAP RFC Library files are found on the system.
-
Determine RFC Library versionRight-click the RFC library DLL file and select Properties, then view the Version tab. Alternatively, check the file metadata or any version information embedded in the library.Affected if The version is 6.40 or 7.00, or the version date is earlier than 20061211.
-
Identify applications using RFC functionalityReview application logs, configuration files, or code that references RFC calls. Look for usage of function modules like RFC_START_PROGRAM or START_PROGRAM in SAP-enabled applications.Affected if Applications are making RFC calls to the SAP system using the vulnerable library.
-
Check network exposure of RFC portsReview firewall rules and network configuration for open ports typically used by SAP RFC (commonly port 3300, 3301, 8000, or custom RFC ports). Use netstat or firewall logs to identify listening RFC services.Affected if RFC ports are exposed to untrusted networks or the internet.
A system is affected if it has SAP RFC Library version 6.40 or 7.0 with a build date before December 11, 2006, and the RFC_START_PROGRAM function is accessible over the network.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the SAP RFC Library patch released after 20061211 or upgrade to a supported version. Additionally, restrict network access to SAP RFC ports and implement input validation on RFC-enabled interfaces.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-1915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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