Skip to content
Heist/ feed
Back to feed
Critical

Apache Jackrabbit RMI access can lead to RCE

Type: advisorySources: OSV

Java object deserialization issue in Jackrabbit webapp/standalone on all platforms allows attacker to remotely execute code via RMIVersions up to (including) 2.20.10 (stable branch) and 2.21.17 (unstable branch) use the component "commons-beanutils", which contains a class that can be used for remote code execution over RMI. Users are advised to immediately update to versions 2.20.11 or 2.21.18. Note that earlier stable branches (1.0.x .. 2.18.x) have been EOLd already and do not receive updates anymore. In general, RMI support can expose vulnerabilities by the mere presence of an exploitable class on the classpath. Even if Jackrabbit itself does not contain any code known to be exploitable anymore, adding other components to your server can expose the same type of problem. We therefore recommend to disable RMI access altogether (see further below), and will discuss deprecating RMI support in future Jackrabbit releases. How to check whether RMI support is enabledRMI support can be over an RMI-specific TCP port, and over an HTTP binding. Both are by default enabled in Jackrabbit webapp/standalone. The native RMI protocol by default uses port 1099. To check whether it is enabled, tools like "netstat" can be used to check. RMI-over-HTTP in Jackrabbit by default uses the path "/rmi". So when running standalone on port 8080, check whether an HTTP GET request on localhost:8080/rmi returns 404 (not enabled) or 200 (enabled). Note that the HTTP path may be different when the webapp i

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2023-37895
Confirmed fixed CVEs
Not specified
Updated in this feed
7 Nov 2026, 00:40 UTC · Revision 1

Source evidence

Apache Jackrabbit RMI access can lead to RCE

core-osv · Original source

Published 25 Jul 2023, 14:02 UTC

Java object deserialization issue in Jackrabbit webapp/standalone on all platforms allows attacker to remotely execute code via RMIVersions up to (including) 2.20.10 (stable branch) and 2.21.17 (unstable branch) use the component "commons-beanutils", which contains a class that can be used for remote code execution over RMI. Users are advised to immediately update to versions 2.20.11 or 2.21.18. Note that earlier stable branches (1.0.x .. 2.18.x) have been EOLd already and do not receive updates anymore. In general, RMI support can expose vulnerabilities by the mere presence of an exploitable class on the classpath. Even if Jackrabbit itself does not contain any code known to be exploitable anymore, adding other components to your server can expose the same type of problem. We therefore recommend to disable RMI access altogether (see further below), and will discuss deprecating RMI support in future Jackrabbit releases. How to check whether RMI support is enabledRMI support can be over an RMI-specific TCP port, and over an HTTP binding. Both are by default enabled in Jackrabbit webapp/standalone. The native RMI protocol by default uses port 1099. To check whether it is enabled, tools like "netstat" can be used to check. RMI-over-HTTP in Jackrabbit by default uses the path "/rmi". So when running standalone on port 8080, check whether an HTTP GET request on localhost:8080/rmi returns 404 (not enabled) or 200 (enabled). Note that the HTTP path may be different when the webapp i

osv:CVE-2023-37895
Complete source record
{
  "id": "364ae41e18e5076fd708a093af291ba41c0c240877708c065add5f0e6e6d9231",
  "url": "https://osv.dev/vulnerability/CVE-2023-37895",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Apache Jackrabbit RMI access can lead to RCE",
    "summary": "Java object deserialization issue in Jackrabbit webapp/standalone on all platforms allows attacker to remotely execute code via RMIVersions up to (including) 2.20.10 (stable branch) and 2.21.17 (unstable branch) use the component \"commons-beanutils\", which contains a class that can be used for remote code execution over RMI. Users are advised to immediately update to versions 2.20.11 or 2.21.18. Note that earlier stable branches (1.0.x .. 2.18.x) have been EOLd already and do not receive updates anymore. In general, RMI support can expose vulnerabilities by the mere presence of an exploitable class on the classpath. Even if Jackrabbit itself does not contain any code known to be exploitable anymore, adding other components to your server can expose the same type of problem. We therefore recommend to disable RMI access altogether (see further below), and will discuss deprecating RMI support in future Jackrabbit releases. How to check whether RMI support is enabledRMI support can be over an RMI-specific TCP port, and over an HTTP binding. Both are by default enabled in Jackrabbit webapp/standalone. The native RMI protocol by default uses port 1099. To check whether it is enabled, tools like \"netstat\" can be used to check. RMI-over-HTTP in Jackrabbit by default uses the path \"/rmi\". So when running standalone on port 8080, check whether an HTTP GET request on localhost:8080/rmi returns 404 (not enabled) or 200 (enabled). Note that the HTTP path may be different when the webapp i",
    "evidence": "osv:CVE-2023-37895",
    "products": [],
    "severity": "critical",
    "structured": {
      "id": "CVE-2023-37895",
      "aliases": [
        "CVE-2023-37895",
        "GHSA-q8cm-3v62-jj79"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/apache/jackrabbit",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "fixed": "ad1f2db8a135e865c38ec5596ff8135e05a99be4"
                },
                {
                  "introduced": "e9dab9ec10203f604f5fb19d60cf49ef7b0cd855"
                },
                {
                  "fixed": "3ca3dffc23509dc3af4edbe5c4aaa4c07473a285"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:apache:jackrabbit:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "1.0.0"
                      },
                      {
                        "fixed": "2.20.11"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "cpe": "cpe:2.3:a:apache:jackrabbit:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "2.21.0"
                      },
                      {
                        "fixed": "2.21.18"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "versions": [
            "jackrabbit-2.21.16"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-37895.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:48.319814861Z",
      "provider": "osv",
      "references": [
        "https://lists.apache.org/list.html?users@jackrabbit.apache.org",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/37xxx/CVE-2023-37895.json",
        "https://lists.apache.org/thread/j03b3qdhborc2jrhdc4d765d3jkh8bfw",
        "https://nvd.nist.gov/vuln/detail/CVE-2023-37895"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-502"
        ],
        "cna_assigner": "apache",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "2.21.0"
                  },
                  {
                    "fixed": "2.21.18"
                  },
                  {
                    "introduced": "1.0.0"
                  },
                  {
                    "fixed": "2.20.11"
                  },
                  {
                    "introduced": "2.21.0"
                  },
                  {
                    "fixed": "2.21.18"
                  },
                  {
                    "introduced": "1.0.0"
                  },
                  {
                    "fixed": "2.20.11"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/37xxx/CVE-2023-37895.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2023-37895",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 516690,
  "published_at": "2023-07-25T14:02:10.036+00:00"
}