dbcve.org
SoapApplication · Apache

CVE-2022-45378

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-14
Fix available
A fix is available. Upgrade to after 2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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
In the default configuration of Apache SOAP, an RPCRouterServlet is available without authentication. This gives an attacker the possibility to invoke methods on the classpath that meet certain criteria. Depending on what classes are available on the classpath this might even lead to arbitrary remote code execution. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

In the default configuration of Apache SOAP, the RPCRouterServlet is exposed without authentication, allowing attackers to make unauthenticated RPC calls that can invoke arbitrary methods on classes present in the classpath. This can lead to remote code execution depending on what classes are available.

MitigationDisable or remove the unauthenticated RPCRouterServlet, or implement authentication at the container level. Since Apache SOAP is end-of-life, consider migrating to a supported SOAP framework.

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
SoapApplication
Affected:<= 2.3

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Apache SOAP is deployed
    Check web application directories (such as WEB-INF/lib or webapps folder) for Apache SOAP libraries (soap.jar, apache-soap.jar, or similar JAR files containing 'org.apache.soap' packages)
    Affected if Apache SOAP libraries are found in the application classpath or web application directory
  2. Determine the Apache SOAP version
    Inspect the SOAP JAR file manifest or class files for version information, or check library filenames for version strings
    Affected if The version is 2.3 or lower, or version information cannot be determined (assume affected)
  3. Locate the RPCRouterServlet configuration
    Examine web.xml or the deployment descriptor for a servlet definition named 'RPCRouterServlet' or 'rpc' mapping to 'org.apache.soap.server.http.RPCRouterServlet'
    Affected if RPCRouterServlet is defined and mapped to a URL pattern (such as /rpc or /soap/rpc)
  4. Check if RPCRouterServlet allows unauthenticated access
    Review the web.xml security-constraint or authentication settings for the RPCRouterServlet URL mapping. If no security-constraint exists for that URL pattern, the endpoint is publicly accessible
    Affected if No security-constraint is defined for the RPCRouterServlet URL pattern, or authentication is explicitly set to NONE

Your environment is affected if Apache SOAP (version 2.3 or lower) is deployed with the RPCRouterServlet exposed and accessible without authentication constraints.

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 2.3
Interim mitigation

Disable or remove the unauthenticated RPCRouterServlet, or implement authentication at the container level. Since Apache SOAP is end-of-life, consider migrating to a supported SOAP framework.

Recommended fix High confidence
  1. Apache SOAP (versions <= 2.3) is no longer maintained by the maintainer according to the official description.
  2. Identify all deployments of Apache SOAP <= 2.3 in your environment.
  3. Since the product is end-of-life with no supported fix, migrate to a currently maintained SOAP implementation such as Apache Axis2, Metro, or CXF.
  4. If migration is not immediately feasible, consider deploying the affected RPCRouterServlet behind a web application firewall (WAF) or reverse proxy with authentication controls.
  5. Alternatively, remove the RPCRouterServlet from the deployment if SOAP services are no longer required.

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

Fix this in Soap 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 the upgrade done

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-2022-45378 — 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-2022-45378 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