Customer Relationship ManagementApplication · Sap

CVE-2014-8669

HIGH · 10.0 CVSS v2.0 Published 2014-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The SAP Promotion Guidelines (CRM-MKT-MPL-TPM-PPG) module for SAP CRM allows remote attackers to execute arbitrary code 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 confidence

CVE-2014-8669 is a critical remote code execution vulnerability in the SAP Promotion Guidelines (CRM-MKT-MPL-TPM-PPG) module of SAP CRM. The vulnerability allows unauthenticated remote attackers to execute arbitrary code on affected systems via unspecified vectors, indicating a severe security flaw in the module's input validation or access controls.

MitigationApply the relevant SAP Security Note to address this RCE vulnerability. Until patched, restrict network access to SAP CRM systems and implement additional monitoring for the Promotion Guidelines module.

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
Customer Relationship ManagementApplication
Affected:all versions

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP CRM installation
    Check system inventory or running services for SAP CRM components. On SAP systems, use transaction code SM37 to list background jobs, or check for SAP CRM processes listening on network ports (typically 8000, 8080, or custom SAP ports).
    Affected if SAP Customer Relationship Management software is installed and running
  2. Verify Promotion Guidelines module is active
    In SAP, use transaction code SE16 or SE11 to query table CRMD_MKT_APPL_OBJ and look for objects related to PPM (Promotion Process Manager) or PPG (Promotion Guidelines). Alternatively, use transaction code SA38 to run report CRM_MKT_ACTIVATE_APPL and check if Promotion Guidelines application is enabled.
    Affected if The Promotion Guidelines module (TPM-PPG/CRM-MKT-MPL-TPM-PPG) is installed and active in the SAP CRM system
  3. Confirm SAP CRM version
    Execute transaction code SM37 and check the SAP system version via transaction code SM51, or use SAPMMC console to view installed product version. Alternatively, check the SAP kernel version by executing 'sapcontrol -nr <instance> -function GetVersion' from the host.
    Affected if Any installed version of SAP Customer Relationship Management is confirmed (per vendor, all versions are affected)
  4. Check module exposure
    Review SAP ICM (Internet Communication Manager) configuration via transaction code SMICM to see which ports and paths are exposed. Specifically look for exposure of /sap/bc/rest/ or /sap/crm/ endpoints that may serve the Promotion Guidelines module.
    Affected if The SAP CRM web interfaces (ICF services) are accessible over network and Promotion Guidelines module is reachable

A user is affected if they have SAP CRM installed with the Promotion Guidelines module (CRM-MKT-MPL-TPM-PPG) enabled and exposed, as all versions of SAP CRM contain this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant SAP Security Note to address this RCE vulnerability. Until patched, restrict network access to SAP CRM systems and implement additional monitoring for the Promotion Guidelines module.

Fix this in Customer Relationship Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-8669 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-8669 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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