CVE-2013-6869
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 · uneditedSQL injection vulnerability in the SRTT_GET_COUNT_BEFORE_KEY_RFC function in SAP NetWeaver 7.30 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in the SRTT_GET_COUNT_BEFORE_KEY_RFC function of SAP NetWeaver 7.30 allows remote attackers to execute arbitrary SQL commands. The vulnerability exists in this RFC function and can be exploited through unspecified vectors, potentially allowing complete database compromise.
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= 7.30CVSS 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.
-
Verify SAP NetWeaver versionExecute SAP transaction code SM51 to display the system version, or use transaction code SAINT and check the System Info section. Confirm the version is exactly 7.30.Affected if The installed SAP NetWeaver version is 7.30 exactly and the SRTT_GET_COUNT_BEFORE_KEY_RFC function is present in the system.
-
Locate the vulnerable RFC functionExecute SAP transaction code SE37 (ABAP Function Modules). In the Function Module field, enter SRTT_GET_COUNT_BEFORE_KEY_RFC and press F7 to display. Alternatively, use transaction code SE80 to search for this function module.Affected if The function module SRTT_GET_COUNT_BEFORE_KEY_RFC exists in the system and is remotely callable.
-
Check RFC authorization for the functionExecute transaction code SM59 (RFC Configuration). Look for RFC destinations that can access the function module. Use transaction code SU01 to check user RFC authorizations for the function module SRTT_GET_COUNT_BEFORE_KEY_RFC.Affected if The function module is remotely accessible via RFC without strict authorization controls.
-
Review system logs for exploitation indicatorsExecute transaction code SM37 (Background Job Overview) to check for unusual jobs. Use transaction code ST03N to review system performance logs. Check transaction code SECLOG for security-related logs for any SQL injection patterns targeting SRTT_GET_COUNT_BEFORE_KEY_RFC.Affected if Logs show unusual or unauthorized SQL commands or excessive calls to the SRTT_GET_COUNT_BEFORE_KEY_RFC function.
You are affected if your SAP NetWeaver version is exactly 7.30 and the SRTT_GET_COUNT_BEFORE_KEY_RFC function module exists and is accessible in your environment.
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 relevant SAP Security Note to patch the vulnerable SRTT_GET_COUNT_BEFORE_KEY_RFC function. As a compensating control, restrict network access to SAP NetWeaver interfaces and implement WAF rules to detect SQL injection attempts until the patch can be deployed.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6869 — 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-2013-6869 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