dbcve.org
WebmethodsApplication · Softwareag

CVE-2023-0925

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Version 10.11 of webMethods OneData runs an embedded instance of Azul Zulu Java 11.0.15 which hosts a Java RMI registry (listening on TCP port 2099 by default) and two RMI interfaces (listening on a single, dynamically assigned TCP high port). Port 2099 serves as a Java Remote Method Invocation (RMI) registry which allows for remotely loading and processing data via RMI interfaces. An unauthenticated attacker with network connectivity to the RMI registry and RMI interface ports can abuse this functionality to instruct the webMethods OneData application to load a malicious serialized Java object as a parameter to one of the available Java methods presented by the RMI interface. Once deserialized on the vulnerable server, the malicious code runs as whichever operating system account is used to run the software, which in most cases is the local System account on Windows.

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

webMethods OneData version 10.11 embeds Azul Zulu Java 11.0.15 with an RMI registry listening on TCP port 2099. The RMI registry accepts deserialized Java objects as parameters to remote method calls, allowing unauthenticated attackers to send malicious serialized payloads that execute arbitrary code on the server with the privileges of the running OS account.

MitigationRestrict network access to port 2099 and RMI high ports via firewall or disable the RMI registry entirely. If a patched version of webMethods OneData is available, upgrade to remove the vulnerable Java component.

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
WebmethodsApplication
Affected:= 10.11

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. Confirm webMethods OneData version
    Check the installed version of webMethods OneData using the Software AG command 'sendmanagesoftwareversion' or by inspecting the product installation directory for version files. Alternatively, check the ' SAGHome/OneData/version.txt' or 'OneData/version' file in the installation directory.
    Affected if The installed version is exactly 10.11 (older versions or patched versions are not affected by this specific CVE)
  2. Verify RMI registry is listening on port 2099
    Run 'netstat -an | grep 2099' or 'ss -tlnp | grep 2099' on the server to check if TCP port 2099 is in LISTEN state. Also check using 'lsof -i :2099' to identify the process.
    Affected if Port 2099 is open and listening, indicating the RMI registry is active and exposed
  3. Check if port 2099 is exposed to network
    Review firewall rules using 'iptables -L -n' or 'firewall-cmd --list-all' to determine if TCP port 2099 is permitted for inbound connections from untrusted networks. Check if the service is bound to 0.0.0.0 rather than localhost.
    Affected if Port 2099 is accessible from network addresses other than localhost or loopback, meaning the RMI registry is network-reachable
  4. Identify bundled Java version
    Locate the embedded Azul Zulu Java within the OneData installation, typically under 'SAGHome/common/jvm' or 'SAGHome/primitives/etc/jvm'. Run 'java -version' from that directory to check if it reports Java 11.0.15.
    Affected if The bundled Azul Zulu Java version is 11.0.15 specifically

You are affected if webMethods OneData version 10.11 is installed, the RMI registry on port 2099 is listening, and port 2099 is network-accessible to untrusted sources.

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

Restrict network access to port 2099 and RMI high ports via firewall or disable the RMI registry entirely. If a patched version of webMethods OneData is available, upgrade to remove the vulnerable Java component.

Fix this in Webmethods Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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