dbcve.org
Genesis64Application · Iconics

CVE-2022-29834

HIGH · 7.5 CVSS v3.1 Published 2022-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Mitsubishi Electric GENESIS64 versions 10.97 to 10.97.1, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97 to 10.97.1, Mitsubishi Electric ICONICS Suite versions 10.97 to 10.97.1, and Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97 to 10.97.1 allows a remote unauthenticated attacker to access to arbitrary files in the GENESIS64 server or ICONICS suite server and disclose information stored in the files by embedding a malicious URL parameter in the URL of the monitoring screen delivered to the GENESIS64 or ICONICS Suite mobile monitoring application and accessing the monitoring screen.

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

A path traversal vulnerability in the GENESIS64 and ICONICS Suite mobile monitoring application allows remote unauthenticated attackers to manipulate URL parameters and access arbitrary files on the server, leading to information disclosure. The vulnerability exists in the monitoring screen URL handling mechanism.

MitigationApply vendor-provided patches for versions 10.97 to 10.97.1. As an interim control, restrict network access to the mobile monitoring application and implement URL filtering at the web application firewall or reverse proxy level.

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
Genesis64Application
Affected:= 10.97= 10.97.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Iconics Genesis64 or ICONICS Suite is installed
    Locate the installation directory or check installed programs list for Genesis64 or ICONICS Suite components. Look for version information in the application's About or Help section, or check the Windows installed programs list.
    Affected if The product is Genesis64 or ICONICS Suite and the exact version is 10.97 or 10.97.1 (or a 10.97.x variant)
  2. Confirm the exact version number
    Access the application properties or check the program's version information file. In Windows, right-click the executable and select Properties, or use the command 'wmic product get name,version' if available.
    Affected if The installed version is exactly 10.97 or 10.97.1
  3. Determine if the mobile monitoring application is enabled
    Check the web server configuration or IIS settings for the mobile monitoring application. Look for services related to mobile monitoring, typically exposed on ports 80/443 or custom ports.
    Affected if The mobile monitoring web interface is accessible and operational
  4. Inspect URL handling for the monitoring screen feature
    Review the web application configuration files or test URL parameter manipulation on the monitoring screen endpoint. Check if parameters controlling screen display accept file path inputs.
    Affected if The monitoring screen URL parameters accept arbitrary path input without proper validation

You are affected if Iconics Genesis64 or ICONICS Suite version 10.97 or 10.97.1 is installed and the mobile monitoring web application is exposed, allowing URL parameter manipulation to access arbitrary files.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for versions 10.97 to 10.97.1. As an interim control, restrict network access to the mobile monitoring application and implement URL filtering at the web application firewall or reverse proxy level.

Fix this in Genesis64 Scoped from the published advisory
  • Consultation10.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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