dbcve.org
GridvisApplication · Janitza

CVE-2023-50895

HIGH · 7.2 CVSS v3.1 Published 2024-03-26
Fix available
A fix is available. Upgrade to 9.0.67 or later.
See remediation →
78/100
Remediation priority · High
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, exposed dangerous methods in the de.janitza.pasw.project.server.ServerDatabaseProject project load functionality allow remote authenticated administrative users to execute arbitrary Groovy code.

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 code injection vulnerability in Janitza GridVis where the project load functionality in the ServerDatabaseProject class exposes dangerous methods that allow authenticated administrative users to execute arbitrary Groovy code, leading to remote code execution.

MitigationUpgrade to a version beyond 9.0.66 when available; until then, restrict administrative access to only trusted users and consider network segmentation to limit exposure.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Locate GridVis installation and identify version
    Check common installation directories (C:\Program Files\Janitza\GridVis or /opt/gridvis) and look for version information in the application executable, about dialog, or version file. GridVis typically stores version data in the application manifest or an about window accessible from the Help menu.
    Affected if The installed GridVis version is lower than 9.0.67 (such as 9.0.66, 9.0.65, etc.)
  2. Confirm ServerDatabaseProject component is in use
    Identify whether the GridVis deployment uses the ServerDatabaseProject functionality. This is typically configured when setting up a server-based project with database backend rather than a local file-based project. Check project configuration files or the GridVis server setup for references to ServerDatabaseProject or database connection strings.
    Affected if The environment uses a server-based project with database backend (ServerDatabaseProject) as opposed to a local file-based project
  3. Verify administrative user access exists
    Check if administrative accounts are configured in GridVis. Administrative users are required for the exploit to work. Review user management settings in GridVis administration panel or check the user configuration database/flat file for accounts with administrative privileges.
    Affected if Administrative user accounts exist and are enabled in GridVis, particularly if those accounts are accessible beyond trusted internal users
  4. Assess network exposure of GridVis service
    Determine if the GridVis server is accessible over the network. Since exploitation requires authenticated administrative access, check if the GridVis web interface or API port is exposed externally or to untrusted networks. Review firewall rules and network segmentation around the GridVis server.
    Affected if The GridVis service is accessible from network segments containing untrusted users, increasing the likelihood that an attacker could reach the authentication mechanism

You are affected if GridVis version is below 9.0.67 AND the ServerDatabaseProject feature is in use AND administrative access is available to potentially untrusted users on the network.

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

Upgrade to a version beyond 9.0.66 when available; until then, restrict administrative access to only trusted users and consider network segmentation to limit exposure.

Recommended fix High confidence

GridVis 9.0.67

  1. Create a complete backup of the current GridVis installation and its database
  2. Download GridVis version 9.0.67 or later from the official Janitza Electronics website
  3. Stop the GridVis service to prevent data corruption during upgrade
  4. Install the new GridVis version 9.0.67 or later following standard installation procedures
  5. After installation, verify the version number matches 9.0.67 or higher
  6. Start the GridVis service and confirm all services are running properly
  7. Validate that the vulnerability is resolved by checking the updated version information

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

Fix this in Gridvis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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