CVE-2013-3244
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 · uneditedMultiple unspecified vulnerabilities in the CJDB_FILL_MEMORY_FROM_PPB function in the Project System (PS-IS) module for SAP ERP Central Component (ECC) allow remote attackers to execute arbitrary code via a (1) RFC or (2) SOAP-RFC request.
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 confidenceThis vulnerability exists in the CJDB_FILL_MEMORY_FROM_PPB function within SAP ECC's Project System (PS-IS) module. Attackers can exploit unspecified flaws by sending malicious RFC or SOAP-RFC requests, enabling remote arbitrary code execution on the SAP system.
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 dataall versionsCVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/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 ECC PS-IS module installationCheck if the Project System (PS-IS) module is installed in your SAP system by reviewing the installed software components via SAP transaction SE16 or by querying table CVERS_SUBTMP for component 'PS-IS'Affected if The PS-IS module is installed and active in the SAP system
-
Confirm RFC endpoint exposureCheck if RFC and SOAP-RFC interfaces are enabled and accessible by reviewing SAP transaction SM59 for RFC destinations and checking for externally exposed SOAP-RFC endpoints in transaction SOAMANAGERAffected if RFC or SOAP-RFC endpoints are configured and reachable from network locations where attackers could send malicious requests
-
Identify the CJDB_FILL_MEMORY_FROM_PPB functionSearch for the function module CJDB_FILL_MEMORY_FROM_PPB in your system using SAP transaction SE37 or by querying table TFDIRAffected if The CJDB_FILL_MEMORY_FROM_PPB function module exists in the system, indicating the vulnerable code is present
-
Review RFC access control configurationExamine SAP ACL configurations for RFC destinations using transaction SM59 and verify the security settings in table RFCDES and the ACL files (saprfc.ini) for allowed external callersAffected if RFC endpoints lack proper ACL restrictions or allow unrestricted external access
-
Check for related security notesReview installed SAP Security Notes using transaction SNOTE or by querying table SNOTEEVT for notes related to CVE-2013-3244 or function CJDB_FILL_MEMORY_FROM_PPBAffected if No relevant SAP Security Note patch has been applied to address this vulnerability
Your environment is affected if SAP ECC with PS-IS module is installed, RFC or SOAP-RFC endpoints are exposed externally or to untrusted networks, and the CJDB_FILL_MEMORY_FROM_PPB function exists without the corresponding security patch 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 the relevant SAP Security Note patch for this vulnerability and implement network segmentation/access controls to restrict RFC and SOAP-RFC endpoint exposure.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3244 — 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-3244 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