dbcve.org
NetweaverApplication · Sap

CVE-2014-6252

MEDIUM · 6.5 CVSS v2.0 Published 2014-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Buffer overflow in disp+work.exe 7000.52.12.34966 and 7200.117.19.50294 in the Dispatcher in SAP NetWeaver 7.00 and 7.20 allows remote authenticated users to cause a denial of service or 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

Buffer overflow vulnerability in SAP NetWeaver Dispatcher (disp+work.exe) versions 7000.52.12.34966 and 7200.117.19.50294 allows remote authenticated attackers to crash the dispatcher or execute arbitrary code via unspecified vectors.

MitigationApply SAP security patches for this vulnerability; restrict network access to SAP dispatcher ports and ensure robust authentication controls are in place.

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
NetweaverApplication
Affected:= 7.0= 7.20

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/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 checks

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

  1. Identify if SAP NetWeaver Dispatcher is running
    Check running processes for disp+work.exe or query SAP Management Console (SAPMMC) for dispatcher status
    Affected if The dispatcher process is active and exposed to network
  2. Determine installed SAP NetWeaver version
    Run sapinfo command or check version via SAPMMC under dispatcher properties
    Affected if Version matches 7000.52.12.34966 or 7200.117.19.50294, or falls within NetWeaver 7.0 or 7.20 release families
  3. Verify dispatcher is network accessible
    Check if dispatcher ports (typically 3200, 3300, 3600, 8000, or as configured) are listening and exposed
    Affected if Dispatcher ports are open to network and authentication is weak or compromised
  4. Confirm authentication status
    Review SAP user authentication configuration for dispatcher access and verify if anonymous or weak credentials could be used
    Affected if Dispatcher accepts connections from unauthenticated or weakly authenticated users

Environment is affected if SAP NetWeaver Dispatcher (disp+work.exe) is running with version 7000.52.12.34966 or 7200.117.19.50294 (or NetWeaver 7.0/7.20 family) and is network-accessible without robust authentication controls.

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 patches for this vulnerability; restrict network access to SAP dispatcher ports and ensure robust authentication controls are in place.

Fix this in Netweaver Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6252 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-6252 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