dbcve.org
Netweaver As Java For Deploy ServiceApplication · Sap

CVE-2023-24527

MEDIUM · 5.3 CVSS v3.1 Published 2023-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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 AS Java for Deploy Service - version 7.5, does not perform any access control checks for functionalities that require user identity enabling an unauthenticated attacker to attach to an open interface and make use of an open naming and directory API to access a service which will enable them to access but not modify server settings and data with no effect on availability and integrity.

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 · high confidence

SAP NetWeaver AS Java Deploy Service version 7.5 lacks access control checks on functionalities requiring user identity, allowing unauthenticated attackers to access an open naming and directory API. This enables unauthorized read-only access to certain server settings and data through an open interface without affecting availability or integrity.

MitigationApply SAP security notes/patches for CVE-2023-24527 and restrict access to the naming and directory API by implementing proper authentication and authorization controls on the affected interface.

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 As Java For Deploy ServiceApplication
Affected:= 7.5

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 SAP NetWeaver AS Java Deploy Service version
    Check the installed version of SAP NetWeaver AS Java Deploy Service in your environment. On Windows, this can be found in the SAP Installed Products directory or via SAP LM. On Unix/Linux, check the version info in the installation directory or via the SAP Management Console.
    Affected if The installed version is exactly 7.5 (Build version 7.5)
  2. Locate the naming and directory API endpoint
    Identify if the JNDI (Java Naming and Directory Interface) or naming and directory API endpoint is exposed on the SAP NetWeaver Java system. Common paths include the /CPIC and /UM/ endpoints or similar administrative interfaces. Check the web.xml and the deployed applications in the SAP NetWeaver Developer Studio.
    Affected if The naming and directory API is accessible via web services or HTTP endpoints without additional configuration required for access control.
  3. Test unauthenticated API access
    Attempt to access the naming and directory API endpoint using a web browser or HTTP client without providing any authentication credentials (username/password). Check if the system returns server settings, directory data, or configuration information without requiring login.
    Affected if The API returns data or responds successfully without requiring authentication credentials, indicating the access control is missing.
  4. Verify if public access is enabled in the security configuration
    Check the SAP NetWeaver AS Java security configuration (via Visual Administrator or NWA) for the specific naming service interface. Look for any security roles or authentication requirements assigned to the naming/directory API functionality.
    Affected if The naming/directory API is configured to allow anonymous or public access without requiring user identity validation.

You are affected if SAP NetWeaver AS Java Deploy Service version 7.5 is running and the naming and directory API is accessible without authentication, allowing unauthorized read-only access to server settings.

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/patches for CVE-2023-24527 and restrict access to the naming and directory API by implementing proper authentication and authorization controls on the affected interface.

Fix this in Netweaver As Java For Deploy Service Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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