CVE-2013-7094
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 RSDDCVER_COUNT_TAB_COLS 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 RSDDCVER_COUNT_TAB_COLS function in SAP NetWeaver 7.30 allows remote unauthenticated attackers to execute arbitrary SQL commands via unspecified vectors.
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.
-
Identify SAP NetWeaver versionCheck the installed SAP NetWeaver version via transaction code ST03, or query the SAP system information using SAPMSSQL or the SAP kernel version checkAffected if The installed version is exactly 7.30 (this specific version is affected; other versions may not be)
-
Locate the RSDDCVER_COUNT_TAB_COLS functionAccess the ABAP Function Builder (transaction SE37) and search for the function module named RSDDCVER_COUNT_TAB_COLS to confirm its presence in the systemAffected if The function module RSDDCVER_COUNT_TAB_COLS exists and is deployed in the system (this is the vulnerable component)
-
Verify if function is exposed to networkCheck SAP Gateway and ICF (Internet Communication Framework) settings to determine if the RSDDCVER_COUNT_TAB_COLS function or its calling endpoint is accessible remotely via HTTP/HTTPS without authenticationAffected if The function or its calling interface is exposed to unauthenticated remote network access (required for the attack vector)
-
Confirm SAP Security Note 1855 applicationUse transaction SNOTE to review installed SAP Security Notes, or check the SAP Support Portal for the patch status of Note 1855 which addresses this specific SQL injection vulnerabilityAffected if SAP Security Note 1855 has NOT been applied to the system (the vulnerability remains unpatched)
-
Review SQL trace for suspicious activityAnalyze SQL traces via transaction ST03N or database audit logs for any unexpected or unauthorized SQL commands that may have been executed through the RSDDCVER_COUNT_TAB_COLS functionAffected if There are unauthorized SQL commands in logs or evidence of SQL injection attempts against this function
The environment is affected if SAP NetWeaver version 7.30 is running, the RSDDCVER_COUNT_TAB_COLS function is present and exposed, and SAP Security Note 1855 has not been applied.
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 SAP Security Note 1855 to patch the vulnerable RSDDCVER_COUNT_TAB_COLS function and sanitize user inputs to prevent SQL injection.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7094 — 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-7094 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