Customer Relationship Management Internet SalesApplication · Sap

CVE-2014-8661

HIGH · 10.0 CVSS v2.0 Developing 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 CRM Internet Sales module allows remote attackers to execute arbitrary 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 · low confidence

The SAP CRM Internet Sales module contains a remote command execution vulnerability allowing unauthenticated attackers to execute arbitrary OS commands. The attack surface appears to be web-facing interfaces in the Internet Sales component, though specific exploitation vectors are not detailed in available sources.

MitigationApply SAP security notes immediately to patch the CRM Internet Sales module. If patches are unavailable, restrict network access to Internet-facing Sales interfaces and implement web application firewall rules to block command injection patterns.

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 Management Internet SalesApplication
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 if SAP CRM Internet Sales is installed
    Check installed SAP modules or components for 'CRM Internet Sales' using SAP transaction code SPAM or check system information via SAP Management Console
    Affected if The CRM Internet Sales component appears in the installed software inventory
  2. Determine if Internet Sales web interfaces are enabled
    Review SAP ICM (Internet Communication Manager) configuration and check for active ICF (Internet Communication Framework) nodes related to Internet Sales (path typically includes /sap/bc/bsp/sap/crm_ics and similar paths)
    Affected if Internet Sales ICF nodes are active and accessible
  3. Check network exposure of SAP web services
    Review firewall rules, load balancer configurations, or network scans to determine if SAP ICM ports (typically 8000, 8080, or 443/80 for HTTP) are exposed to untrusted networks or the internet
    Affected if Port 8000, 8080, or standard HTTP/HTTPS ports serving SAP are accessible from untrusted/external networks
  4. Verify if SAP CRM is accessible without authentication
    Attempt to access common Internet Sales URLs (such as /sap/bc/bsp/sap/crm_ics or /sap/public/icman) from an external perspective or review anonymous access configuration in SAP
    Affected if Anonymous or unauthenticated access to CRM Internet Sales endpoints is permitted

If SAP CRM Internet Sales module is installed and its web-facing interfaces are network-accessible without requiring authentication, the environment is affected by 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 SAP security notes immediately to patch the CRM Internet Sales module. If patches are unavailable, restrict network access to Internet-facing Sales interfaces and implement web application firewall rules to block command injection patterns.

Fix this in Customer Relationship Management Internet Sales Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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 locally
dbcve dependency scanner

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