dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-34143

CRITICAL · 9.3 CVSS v4.0 Published 2025-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An authentication bypass vulnerability exists in ETQ Reliance on the CG (legacy) platform. The application allowed login as the privileged internal SYSTEM user by manipulating the username field. The SYSTEM account does not require a password, enabling attackers with network access to the login page to obtain elevated access. Once authenticated, an attacker could achieve remote code execution by modifying Jython scripts within the application. This issue was resolved by introducing stricter validation logic to exclude internal accounts from public authentication workflows in version MP-4583.

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

ETQ Reliance CG (legacy) platform allows authentication bypass via username field manipulation to login as the privileged SYSTEM user without a password. Successful authentication enables remote code execution through modification of Jython scripts within the application.

MitigationUpgrade to version MP-4583 or later which implements stricter validation logic to exclude internal accounts from public authentication workflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 ETQ Reliance CG installation
    Locate the application installation directory and confirm it is the legacy Reliance CG platform (not a newer version). Check product version in about or system information panel.
    Affected if Running legacy Reliance CG version prior to MP-4583
  2. Verify SYSTEM user account exists
    Query the user database or examine user configuration files for the presence of a SYSTEM or admin-level account.
    Affected if SYSTEM privileged account exists in the user repository
  3. Confirm Jython script functionality is enabled
    Check if the Jython scripting module is installed and accessible within the application. Look for script editor or automation features that allow modifying .py files.
    Affected if Jython script modification capability is available to authenticated users
  4. Review authentication configuration
    Examine authentication configuration files or settings to determine whether internal/system accounts are excluded from public-facing login workflows.
    Affected if Internal accounts like SYSTEM are not properly excluded from authentication
  5. Test for authentication bypass
    Attempt to authenticate using the username 'SYSTEM' with an empty or incorrect password against the login endpoint.
    Affected if Authentication succeeds with SYSTEM username and no valid password

A user is affected if running legacy Reliance CG prior to MP-4583 where the SYSTEM account can be accessed via username manipulation without a password.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version MP-4583 or later which implements stricter validation logic to exclude internal accounts from public authentication workflows.

Recommended fix Moderate confidence

ETQ Reliance CG platform MP-4583 or later

  1. Identify current installed version of ETQ Reliance (CG/legacy platform)
  2. Contact ETQ support or consult official release notes to obtain version MP-4583 or later
  3. Plan upgrade during maintenance window due to potential brief service interruption
  4. Backup current application configuration and any custom Jython scripts
  5. Deploy upgrade to MP-4583 or latest stable release
  6. Verify SYSTEM account can no longer be accessed through standard login page
  7. Test that legitimate authentication workflows still function correctly
  8. Confirm Jython script execution is restricted to authorized internal accounts only

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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