CVE-2015-3979
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 · uneditedUnspecified vulnerability in the Business Rules Framework (CRM-BF-BRF) in SAP CRM allows attackers to execute arbitrary code via unknown vectors, aka SAP Security Note 2097534.
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 confidenceVulnerability in SAP CRM's Business Rules Framework (CRM-BF-BRF) allows unauthenticated attackers to execute arbitrary code via unspecified vectors in the business rules processing engine. The flaw enables remote code execution within the SAP CRM application context.
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
- 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.
-
Confirm SAP CRM installationVerify that SAP Customer Relationship Management is installed in your environment by checking SAP system information via transaction SM37 or by reviewing SAP system landscape documentationAffected if SAP CRM is not installed in the environment, the system is not affected by this specific vulnerability
-
Identify Business Rules Framework componentCheck if the Business Rules Framework (BRF/BRF+) component CRM-BF-BRF is active in your SAP CRM system using transaction SE11 to view system components or via SAP Solution ManagerAffected if The CRM-BF-BRF component is not present or not activated in the SAP CRM system
-
Check if patch has been appliedUse transaction SNOTE or search for SAP Security Note 2097534 in the SAP system to verify whether the security patch for this vulnerability has been implementedAffected if SAP Security Note 2097534 has NOT been applied to the system, indicating the vulnerability remains unpatched
-
Review BRF configuration for unauthorized rulesExamine active business rules configurations in the BRF+ workbench (transaction BRFPLUS) for any unauthorized or unexpected rule definitions, particularly rules that could execute code or system commandsAffected if Unexpected or unauthorized business rules are found that could enable arbitrary code execution
The environment is affected if SAP CRM with the Business Rules Framework (CRM-BF-BRF) is installed and SAP Security Note 2097534 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 2097534 to patch the Business Rules Framework vulnerability. Review and test business rule configurations post-patch to ensure functionality is preserved.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3979 — 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-2015-3979 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