dbcve.org
IsisApplication · Apache

CVE-2022-42466

MEDIUM · 6.1 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Prior to 2.0.0-M9, it was possible for an end-user to set the value of an editable string property of a domain object to a value that would be rendered unchanged when the value was saved. In particular, the end-user could enter javascript or similar and this would be executed. As of this release, the inputted strings are properly escaped when rendered.

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 stored Cross-Site Scripting (XSS) vulnerability in the application's rendering layer. Prior to version 2.0.0-M9, editable string properties of domain objects were rendered without proper HTML encoding, allowing users to inject JavaScript code (e.g., via <script> tags or javascript: URIs) that would execute when other users viewed the data. The fix involves applying proper output encoding/escaping when rendering string values.

MitigationUpgrade to version 2.0.0-M9 or later. If upgrading is not immediately possible, implement output encoding for all user-supplied string values at the view/rendering layer to prevent XSS execution.

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
IsisApplication
Affected:< 2.0.0= 2.0.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Apache Isis version
    Locate the Apache Isis version in your project build file (pom.xml, gradle.build) or the isis-core JAR manifest. Compare against the affected range: versions below 2.0.0 or exactly 2.0.0.
    Affected if The installed version is less than 2.0.0 or exactly equal to 2.0.0
  2. Find editable string properties in domain objects
    Review your domain entity classes. Identify any String-typed properties that are editable (not explicitly disabled via @Property(editing=Disabled) or hidden). These are the data fields that could carry malicious scripts.
    Affected if Your domain model contains editable String-type properties that get rendered to end users
  3. Inspect the rendering/view layer for output encoding
    Examine your view layer configuration (Wicket viewer, Restful Objects API, or custom viewers) to determine whether string values are passed through HTML encoding or escaping functions before display. Look for any custom rendering logic that may or may not apply encoding.
    Affected if String values are rendered without HTML encoding/escaping applied at the view layer
  4. Check if user-supplied strings are stored and displayed to other users
    Trace the data flow: verify whether users can input or modify string property values that are subsequently displayed to other users in the application UI. This is the prerequisite for stored XSS to trigger.
    Affected if Users can store string content that is later rendered to other users without encoding

Your environment is affected if you run Apache Isis version < 2.0.0 or = 2.0.0 and your application renders editable string properties to users without output encoding at the rendering layer.

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

Upgrade to version 2.0.0-M9 or later. If upgrading is not immediately possible, implement output encoding for all user-supplied string values at the view/rendering layer to prevent XSS execution.

Recommended fix High confidence

2.0.0-M9 or later stable release

  1. 1. Identify the current Apache Isis version in use by checking project dependencies or pom.xml
  2. 2. If using a version < 2.0.0-M9 or exactly 2.0.0, plan an upgrade to version 2.0.0-M9 or later
  3. 3. Update the version in your build configuration (Maven pom.xml or Gradle build file) to 2.0.0-M9 or a later stable release
  4. 4. Run build and test suite to verify application functionality after upgrade
  5. 5. Verify that user input in editable string properties is now properly escaped when rendered
Caveat Review release notes for 2.0.0-M9 for any breaking changes or API modifications

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

Fix this in Isis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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