Document Management ServicesApplication · Sap

CVE-2014-8660

HIGH · 7.2 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 →
77/100
Remediation priority · High
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
SAP Document Management Services allows local users 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 · moderate confidence

SAP Document Management Services contains a local privilege escalation vulnerability allowing authenticated local users to execute arbitrary commands. The specific attack vector is not disclosed, but the vulnerability enables local users to escalate privileges beyond their assigned permissions, likely through improper input validation or insufficient access controls within the DMS component.

MitigationApply the relevant SAP security patch for CVE-2014-8660 and restrict local user permissions to DMS services. If a patch is unavailable, consider network segmentation to limit local access and monitor for suspicious command execution.

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
Document Management ServicesApplication
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
Local
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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 Document Management Services is installed
    Locate SAP DMS components on the system using SAP management tools, installed software inventory, or by checking for SAP-related processes and services running on the host
    Affected if SAP DMS is found to be installed and running on the system
  2. Confirm the SAP DMS version
    Use SAP administration tools (such as SAP Management Console, SAP MMC, or SAP's software lifecycle management) to retrieve the installed version of Document Management Services
    Affected if Any version of SAP Document Management Services is identified (all versions are affected)
  3. Verify local user authentication is possible
    Check if local user accounts have access to the SAP DMS application by attempting to authenticate with local credentials or reviewing user access configurations in SAP DMS security settings
    Affected if Local users can authenticate to SAP DMS with any privilege level
  4. Review system logs for suspicious command execution
    Examine SAP DMS logs, system event logs, and shell history files for unexpected commands, scripts, or processes spawned by the DMS service or associated user sessions
    Affected if Logs show command execution patterns inconsistent with normal DMS operations or commands executed by lower-privileged local users
  5. Check for privilege escalation indicators
    Audit user permissions, group memberships, and access rights before and after suspected exploitation. Look for local users who have gained elevated SAP or system-level privileges unexpectedly
    Affected if Local users possess privileges beyond their assigned SAP DMS permissions or have gained administrative access they should not have

A user is affected if SAP Document Management Services is installed and running, regardless of version, since all versions contain this vulnerability and local authenticated users can escalate privileges within the DMS component.

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 patch for CVE-2014-8660 and restrict local user permissions to DMS services. If a patch is unavailable, consider network segmentation to limit local access and monitor for suspicious command execution.

Fix this in Document Management Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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