dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Netweaver Application Server JavaApplication · Sap

CVE-2010-5326

CRITICAL · 10.0 CVSS v3.1 Published 2016-05-13
Fix available
A fix is available. Upgrade to after 7.30 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
The Invoker Servlet on SAP NetWeaver Application Server Java platforms, possibly before 7.3, does not require authentication, which allows remote attackers to execute arbitrary code via an HTTP or HTTPS request, as exploited in the wild in 2013 through 2016, aka a "Detour" attack.

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

The Invoker Servlet in SAP NetWeaver Application Server Java (versions prior to 7.3) lacks authentication enforcement, allowing unauthenticated remote attackers to execute arbitrary code through direct HTTP/HTTPS requests. This critical flaw was actively exploited in the wild from 2013-2016 as the 'Detour' attack.

MitigationDisable or properly secure the Invoker Servlet via SAP configuration settings, apply relevant SAP Security Notes/patches, and restrict network access to the SAP Java stack until remediation is complete.

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 Application Server JavaApplication
Affected:<= 7.30

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

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 AS Java is installed
    Check for SAP NetWeaver Java processes running on the system (e.g., using 'ps -ef | grep java' or checking Windows services). Look for SAP J2EE Engine processes.
    Affected if SAP NetWeaver Application Server Java is installed and running.
  2. Determine the SAP NetWeaver AS Java version
    Check the SAP NetWeaver version by inspecting the installed software components. Typically found in SAP META directory, SAP installer logs, or via SAP NWA (NetWeaver Administrator) at https://<host>:<port>/nwa. Look for version information indicating 7.30 or earlier.
    Affected if The installed version is 7.30 or any version lower than 7.3.
  3. Verify if Invoker Servlet is accessible
    Attempt to access the Invoker Servlet endpoint: https://<host>:<port>/invoke/ (or /servlet/invoke). This endpoint should not be reachable without authentication on a patched system.
    Affected if The /invoke/ endpoint responds without requiring authentication, indicating the Invoker Servlet is exposed.
  4. Inspect web.xml for Invoker Servlet configuration
    Locate and examine the web.xml deployment descriptor for the affected web applications. In SAP NetWeaver, this is typically found in the usr/sap/<SID>/<instance>/j2ee/cluster/apps directory or via the SAP Developer traces. Look for 'InvokerServlet' or servlet mapping to '/invoke/*'.
    Affected if The web.xml contains an Invoker Servlet mapping that allows unauthenticated access to arbitrary servlets.

A system is affected if it runs SAP NetWeaver Application Server Java version 7.30 or earlier AND has the Invoker Servlet accessible without authentication (the /invoke endpoint responds without credentials).

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.30
Interim mitigation

Disable or properly secure the Invoker Servlet via SAP configuration settings, apply relevant SAP Security Notes/patches, and restrict network access to the SAP Java stack until remediation is complete.

Recommended fix High confidence

SAP NetWeaver Application Server Java 7.31 or higher (recommended: 7.40/7.50 series)

  1. 1. Identify the current SAP NetWeaver Application Server Java version using SAP JVM or SAP MMC
  2. 2. Download and apply the latest SAP NetWeaver Application Server Java security patch from service.sap.com
  3. 3. Alternatively, upgrade to SAP NetWeaver 7.40 or higher which includes the fix for the Invoker Servlet authentication issue
  4. 4. After patching/upgrading, verify that the Invoker Servlet now requires authentication by attempting an unauthenticated request to the /invoke/ endpoint
  5. 5. Ensure the SAP system is restarted after applying the patch
  6. 6. Review SAP Note 1445998 (or newer relevant security notes) for specific configuration changes needed
Caveat Upgrading to major version 7.40+ may require compatibility testing of custom applications; some deprecated APIs from 7.30 may need updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netweaver Application Server Java Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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