CVE-2022-42467
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 · uneditedWhen running in prototype mode, the h2 webconsole module (accessible from the Prototype menu) is automatically made available with the ability to directly query the database. It was felt that it is safer to require the developer to explicitly enable this capability. As of 2.0.0-M8, this can now be done using the 'isis.prototyping.h2-console.web-allow-remote-access' configuration property; the web console will be unavailable without setting this configuration. As an additional safeguard, the new 'isis.prototyping.h2-console.generate-random-web-admin-password' configuration parameter (enabled by default) requires that the administrator use a randomly generated password to use the console. The password is printed to the log, as "webAdminPass: xxx" (where "xxx") is the password. To revert to the original behaviour, the administrator would therefore need to set these configuration parameter: isis.prototyping.h2-console.web-allow-remote-access=true isis.prototyping.h2-console.generate-random-web-admin-password=false Note also that the h2 webconsole is never available in production mode, so these safeguards are only to ensure that the webconsole is secured by default also in prototype mode.
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 confidenceIn Apache Isis versions before 2.0.0-M8, the H2 database web console was automatically enabled in prototype mode with remote access and no authentication, allowing unauthenticated attackers to execute arbitrary SQL queries against the database.
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< 2.0.0= 2.0.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Apache Isis versionCheck the version of Apache Isis deployed in your environment (typically found in pom.xml, manifest files, or application startup logs)Affected if The installed version is less than 2.0.0 or exactly equals 2.0.0
-
Verify whether the H2 console is enabledCheck if the H2 database web console feature is accessible in your deploymentAffected if The H2 console is accessible and running in prototype mode
-
Inspect the isis.prototyping.h2-console.web-allow-remote-access settingExamine your application configuration (properties file or YAML) for the property isis.prototyping.h2-console.web-allow-remote-accessAffected if This property is set to true or the H2 console is accessible from remote network locations without restriction
-
Verify H2 console authentication configurationCheck for the presence and value of isis.prototyping.h2-console.generate-random-web-admin-password in your configurationAffected if This property is missing, disabled, or a static password is configured for H2 console access
Your environment is affected if you run Apache Isis version 2.0.0 or earlier with the H2 console enabled in prototype mode, particularly if remote access is allowed or authentication is not enforced.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.0.0
Upgrade to version 2.0.0-M8 or later and ensure the default security settings are maintained: do not set isis.prototyping.h2-console.web-allow-remote-access=true unless explicitly required, and keep isis.prototyping.h2-console.generate-random-web-admin-password enabled.
Apache Isis 2.0.0 or later (including 2.0.0-M8 which introduced the fix)
- Upgrade Apache Isis to version 2.0.0 or later (version 2.0.0-M8 introduced the security fix)
- After upgrade, the H2 web console is disabled by default in prototype mode; to enable it, set configuration property isis.prototyping.h2-console.web-allow-remote-access=true
- By default, a random password is now required for H2 console access; find this password in the logs as 'webAdminPass: xxx'
- If you need to revert to the old behavior (no password), additionally set isis.prototyping.h2-console.generate-random-web-admin-password=false
- Verify the H2 console is not accessible in production mode (this is enforced automatically)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-42467 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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