dbcve.org
CayenneApplication · Apache

CVE-2022-24289

HIGH · 8.8 CVSS v3.1 Published 2022-02-11
Fix available
A fix is available. Upgrade to 4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Hessian serialization is a network protocol that supports object-based transmission. Apache Cayenne's optional Remote Object Persistence (ROP) feature is a web services-based technology that provides object persistence and query functionality to 'remote' applications. In Apache Cayenne 4.1 and earlier, running on non-current patch versions of Java, an attacker with client access to Cayenne ROP can transmit a malicious payload to any vulnerable third-party dependency on the server. This can result in arbitrary code execution.

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

This is a Java deserialization vulnerability in Apache Cayenne's Remote Object Persistence (ROP) feature that uses Hessian serialization. An attacker with client access to the Cayenne ROP service can send malicious serialized payloads that get deserialized by vulnerable third-party libraries on the server, leading to arbitrary code execution (RCE). The vulnerability affects Apache Cayenne 4.1 and earlier running on outdated Java versions.

MitigationUpgrade Apache Cayenne to a patched version if available, or disable the ROP feature if not required. Ensure Java is updated to a current supported version, and restrict network access to the ROP endpoint to trusted clients only.

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
CayenneApplication
Affected:< 4.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Apache Cayenne version
    Locate the cayenne jar file in your application classpath or build configuration (pom.xml, gradle dependencies, or the deployed lib directory) and note the exact version number
    Affected if The version is 4.1 or any version lower than 4.2
  2. Verify if the ROP (Remote Object Persistence) feature is enabled
    Inspect your server configuration files and look for ROP server setup - typically involves Hessian serialization endpoints or ROP-specific configuration classes (such as CayenneRemoteService or custom ROP servlet configurations)
    Affected if The ROP feature is configured and running as a server endpoint
  3. Determine the Java runtime version
    Run 'java -version' on the server or check the JRE/JDK version configured in your application runtime environment
    Affected if The Java version is outdated and no longer supported (e.g., Java 8u271 or earlier, or older major Java versions)
  4. Assess network exposure of the ROP service
    Review your network configuration, firewall rules, and service bindings to determine if the ROP endpoint is accessible from untrusted network segments
    Affected if The ROP endpoint is exposed to untrusted or public network access without proper authentication or network-level restrictions

Your environment is affected if you run Apache Cayenne versions below 4.2 with the ROP feature enabled, especially on outdated Java versions and with the ROP endpoint accessible to untrusted clients.

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 4.2 or later
Fixed in 4.2
Interim mitigation

Upgrade Apache Cayenne to a patched version if available, or disable the ROP feature if not required. Ensure Java is updated to a current supported version, and restrict network access to the ROP endpoint to trusted clients only.

Recommended fix Moderate confidence

Apache Cayenne 4.2

  1. 1. Identify all Apache Cayenne deployments in your environment and confirm which ones use the Remote Object Persistence (ROP) feature
  2. 2. Review your dependency management to locate the current Apache Cayenne version (likely version 4.1 or earlier)
  3. 3. Upgrade Apache Cayenne to version 4.2 or later
  4. 4. After upgrading, test the ROP functionality to ensure normal operations continue
  5. 5. If immediate upgrade is not feasible, disable the ROP feature if not required, and implement network segmentation to limit ROP client access to trusted sources only

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

Fix this in Cayenne Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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