Netweaver Java Application ServerApplication · Sap

CVE-2014-3133

MEDIUM · 5.0 CVSS v2.0 Published 2014-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Java Application Server does not properly restrict access, which allows remote attackers to obtain the list of SAP systems registered on an SLD via an unspecified webdynpro, related to SystemSelection.

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 Netweaver Java Application Server contains an information disclosure vulnerability where an unspecified webdynpro component related to SystemSelection fails to properly restrict access. This allows remote unauthenticated attackers to obtain a list of SAP systems registered on the System Landscape Directory (SLD) through the vulnerable endpoint.

MitigationImplement proper authentication and authorization controls on the affected webdynpro component to ensure only authorized users can access the SLD system listing functionality. Restrict access to the SystemSelection-related endpoints to legitimate users.

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
Netweaver Java Application ServerApplication
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
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. Confirm SAP Netweaver Java Application Server is running
    Identify processes or services running SAP Netweaver Java AS in your environment using system inventory tools or by reviewing running Java processes that expose port HTTP/HTTPS typical of SAP Netweaver
    Affected if SAP Netweaver Java Application Server is present in the environment
  2. Locate webdynpro endpoints related to SystemSelection
    Review deployed webdynpro applications on the SAP Netweaver Java AS and identify components with SystemSelection functionality. This may require access to the SAP Netweaver Administrator or reviewing the application deployment descriptors
    Affected if A webdynpro component named SystemSelection or related to system selection is deployed and accessible
  3. Test unauthenticated access to SLD listing functionality
    Attempt to access the SystemSelection-related endpoint without providing any authentication credentials. This can be done by making an HTTP request to the suspected endpoint using a web browser or curl tool without passing any session cookies or authentication headers
    Affected if The endpoint returns a list of SAP systems registered on the System Landscape Directory without requiring login credentials
  4. Verify SLD data exposure
    Examine the response from the unauthenticated request to confirm it contains a listing of SAP systems from the System Landscape Directory, including system names, types, or other SLD registration details
    Affected if The response includes SLD system listing data such as system names, SID, or other registered system information to an unauthenticated user

If SAP Netweaver Java Application Server is running and the SystemSelection webdynpro endpoint is accessible without authentication, the environment is affected by this information disclosure 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

Implement proper authentication and authorization controls on the affected webdynpro component to ensure only authorized users can access the SLD system listing functionality. Restrict access to the SystemSelection-related endpoints to legitimate users.

Fix this in Netweaver Java Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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