dbcve.org
Shardingsphere Elasticjob UiApplication · Apache

CVE-2022-31764

HIGH · 8.5 CVSS v3.1 Published 2025-02-06
Fix available
A fix is available. Upgrade to 3.0.2 or later.
See remediation →
91/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
The Lite UI of Apache ShardingSphere ElasticJob-UI allows an attacker to perform RCE by constructing a special JDBC URL of H2 database. This issue affects Apache ShardingSphere ElasticJob-UI version 3.0.1 and prior versions. This vulnerability has been fixed in ElasticJob-UI 3.0.2. The premise of this attack is that the attacker has obtained the account and password. Otherwise, the attacker cannot perform this attack.

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

Apache ShardingSphere ElasticJob-UI Lite UI contains a remote code execution vulnerability where an authenticated attacker can execute arbitrary code by constructing a malicious JDBC URL when configuring an H2 database connection. The vulnerability is fixed in version 3.0.2.

MitigationUpgrade to ElasticJob-UI version 3.0.2 or later. Since this attack requires valid credentials, enforce strong password policies and consider implementing network segmentation or MFA for administrative interfaces.

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
Shardingsphere Elasticjob UiApplication
Affected:< 3.0.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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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 if ElasticJob-UI is deployed
    Locate the ElasticJob-UI application installation or service in your environment. Check for processes or services related to elasticjob-ui or the Apache ShardingSphere ElasticJob UI component.
    Affected if ElasticJob-UI is present in the environment and its version is below 3.0.2
  2. Determine the installed version
    Inspect the application metadata, build artifacts, or version file within the ElasticJob-UI installation directory. Compare the found version number against the affected range of versions prior to 3.0.2.
    Affected if The installed version is any version lower than 3.0.2
  3. Verify Lite UI is accessible
    Check network configuration or service bindings to determine if the Lite UI web interface is exposed and reachable over the network. Review any proxy or firewall rules that may allow access.
    Affected if The Lite UI is network-accessible without additional authentication barriers beyond the application login
  4. Confirm authentication is required for UI access
    Verify that the Lite UI requires valid user credentials for access. Check if default credentials are in use or if the authentication module is properly configured.
    Affected if The Lite UI can be accessed with default credentials or weak passwords, or authentication can be bypassed entirely

A user is affected if ElasticJob-UI version is below 3.0.2 and the Lite UI is network-accessible with valid credentials, allowing an authenticated attacker to supply a malicious H2 JDBC URL for code execution.

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

Upgrade to ElasticJob-UI version 3.0.2 or later. Since this attack requires valid credentials, enforce strong password policies and consider implementing network segmentation or MFA for administrative interfaces.

Recommended fix High confidence

ElasticJob-UI 3.0.2

  1. 1. Stop the running Apache ShardingSphere ElasticJob-UI service
  2. 2. Back up the current ElasticJob-UI configuration and data directories
  3. 3. Download Apache ShardingSphere ElasticJob-UI version 3.0.2 from the Apache archive (e.g., https://archive.apache.org/dist/shardingsphere/elasticjob-3.0.2/)
  4. 4. Remove the old ElasticJob-UI installation files
  5. 5. Extract the new 3.0.2 version to the installation directory
  6. 6. Restore the backed-up configuration files to the new installation
  7. 7. Start the ElasticJob-UI service
  8. 8. Verify the service is running correctly and the UI is accessible

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

Fix this in Shardingsphere Elasticjob Ui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

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