NetweaverApplication · Sap

CVE-2014-3787

MEDIUM · 5.0 CVSS v2.0 Published 2014-05-19
Fix available
A fix is available. Upgrade to after 7.20 or later.
See remediation →
59/100
Remediation priority · Elevated
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
SAP NetWeaver 7.20 and earlier allows remote attackers to read arbitrary SAP Central User Administration (SAP CUA) tables 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

This is an information disclosure vulnerability in SAP NetWeaver 7.20 and earlier affecting the SAP Central User Administration (CUA) component. The flaw allows remote unauthenticated attackers to read arbitrary tables in the SAP CUA database, potentially exposing sensitive user administration data including user credentials, roles, and organizational assignments.

MitigationApply available SAP security patches for this vulnerability (check SAP Security Notes) and upgrade to a supported NetWeaver version beyond 7.20. Additionally, restrict network access to SAP CUA interfaces and review access logs for signs of exploitation.

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.20= 7.0= 7.01= 7.02= 7.03= 7.10

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
Partial
Integrity
None
Availability
None

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

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 installed SAP NetWeaver version
    Execute transaction code 'SM51' in the SAP GUI or use the SAP NetWeaver Administrator (NWA) console to view the NetWeaver release and version information. Alternatively, check the kernel version via 'disp+work -v' or the SAP system profile parameters.
    Affected if The version is 7.20 or earlier, or specifically 7.0, 7.01, 7.02, 7.03, or 7.10.
  2. Verify SAP CUA component is configured
    Check if Central User Administration is active by accessing transaction code 'SCUA' (CUA Central Configuration) or 'SCUM' (CUA User Maintenance). Also verify distribution model via transaction 'SCUL'.
    Affected if The CUA component is configured and active in the SAP system.
  3. Check network exposure of CUA interfaces
    Review SAP gateway and ICM (Internet Communication Manager) configurations. Use transaction 'SMGW' to check gateway connections and 'SMICM' to review ICM exposure. Verify if port 33xx (SAP Dispatcher) and 48xx (Message Server) are accessible from untrusted networks.
    Affected if CUA interfaces are exposed to untrusted or public networks without proper access controls.
  4. Examine system logs for unauthorized table access
    Review transaction code 'SE16' (Data Browser) access logs via 'SCU3' or check system trace (transaction 'ST01' or 'SM37'). Look for suspicious SELECT queries against tables like USR02, AGR_USERS, ADR6, or other user administration tables originating from unauthenticated or unexpected sources.
    Affected if Logs show SELECT statements on sensitive CUA tables from unknown clients or without proper authentication.

The environment is affected if running SAP NetWeaver version 7.20 or earlier with the CUA component enabled and exposed, particularly if the system is reachable from untrusted networks without proper access restrictions.

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
Upgrade available Upgrade to a release after 7.20
Interim mitigation

Apply available SAP security patches for this vulnerability (check SAP Security Notes) and upgrade to a supported NetWeaver version beyond 7.20. Additionally, restrict network access to SAP CUA interfaces and review access logs for signs of exploitation.

Fix this in Netweaver Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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