dbcve.org
GridvisApplication · Janitza

CVE-2023-50894

HIGH · 8.8 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to 9.0.67 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
In Janitza GridVis through 9.0.66, use of hard-coded credentials in the de.janitza.pasw.feature.impl.activators.PasswordEncryption password encryption function allows remote authenticated administrative users to discover cleartext database credentials contained in error report information.

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 · moderate confidence

Janitza GridVis through 9.0.66 contains hard-coded credentials embedded in the PasswordEncryption function (de.janitza.pasw.feature.impl.activators.PasswordEncryption). Remote authenticated administrative users can exploit this to obtain cleartext database credentials by retrieving error report information that exposes the credentials due to this insecure implementation.

MitigationRemove hard-coded credentials from the PasswordEncryption function and implement proper credential management (e.g., externalized secrets, vault integration). Review all error reporting to ensure sensitive credentials are not exposed. Update to patched version if available.

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
GridvisApplication
Affected:< 9.0.67

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. Determine GridVis installation version
    Locate the GridVis installation directory and check the version. This is typically found in an 'about' dialog within the application, a version info file, or the application executable metadata. Compare against the affected range: versions prior to 9.0.67 are vulnerable.
    Affected if GridVis version is lower than 9.0.67
  2. Locate the PasswordEncryption class
    Search for the file de.janitza.pasw.feature.impl.activators.PasswordEncryption within the GridVis installation directory or application JAR files. This class is part of the Janitza PASW feature implementation.
    Affected if The PasswordEncryption class file exists in the GridVis installation
  3. Inspect PasswordEncryption for hard-coded credentials
    Decompile or inspect the PasswordEncryption class and examine the PasswordEncryption function implementation. Look for hard-coded string literals, encryption keys, or credential constants embedded directly in the source code or compiled bytecode.
    Affected if Hard-coded credentials, encryption keys, or sensitive string constants are found within the PasswordEncryption function
  4. Check error reporting exposure
    Identify if error report generation or export functionality is accessible to administrative users. Check configuration files or web interface endpoints that produce error reports, diagnostic exports, or stack traces that may include application internals.
    Affected if Error report or diagnostic export functionality is accessible and returns sensitive information including database credentials

A user is affected if GridVis version is below 9.0.67 AND the PasswordEncryption class contains hard-coded credentials that can be retrieved through accessible error reporting.

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

Remove hard-coded credentials from the PasswordEncryption function and implement proper credential management (e.g., externalized secrets, vault integration). Review all error reporting to ensure sensitive credentials are not exposed. Update to patched version if available.

Recommended fix High confidence

9.0.67

  1. Backup the current GridVis installation and all associated data/database
  2. Download GridVis version 9.0.67 from the official Janitza website or trusted distribution channel
  3. Stop the GridVis service
  4. Install or upgrade to GridVis version 9.0.67
  5. Start the GridVis service
  6. Verify the password encryption function no longer exposes credentials in error reports

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

Fix this in Gridvis Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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