dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-1098

HIGH · 7.8 CVSS v3.1 Published 2022-04-01
Fix available
A fix is available. Upgrade to 1.8.02.004 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Delta Electronics DIAEnergie (all versions prior to 1.8.02.004) are vulnerable to a DLL hijacking condition. When combined with the Incorrect Default Permissions vulnerability of 4.2.2 above, this makes it possible for an attacker to escalate privileges

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

Delta Electronics DIAEnergie versions prior to 1.8.02.004 are vulnerable to DLL hijacking, where the application loads dynamic link libraries from attacker-controllable locations. When combined with an incorrect default permissions vulnerability in the same product, an authenticated local attacker can escalate privileges by placing a malicious DLL in the application's search path.

MitigationUpdate DIAEnergie to version 1.8.02.004 or later. Additionally, review and remediate file system permissions on the application directory to prevent unauthorized write access.

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
DiaenergieApplication
Affected:< 1.8.02.004

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 DIAEnergie installation directory
    Search for the DIAEnergie installation using 'dir /s C:\*DIAEnergie*' or check common installation paths such as C:\Program Files\Delta Electronics\DIAEnergie or C:\Program Files (x86)\Delta Electronics\DIAEnergie. Also check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'DIAEnergie' to find the InstallLocation.
    Affected if DIAEnergie is not found on the system, so the product is not installed.
  2. Determine installed version
    Once the installation directory is found, locate the main executable (commonly DIAEnergie.exe or similar). Right-click the executable, select Properties, and check the Details tab for the Product Version. Alternatively, check the Uninstall registry entry for the DisplayVersion value.
    Affected if The displayed version is lower than 1.8.02.004 (for example, 1.7.x.x or 1.8.0.x).
  3. Verify DLL hijacking path vulnerability
    Examine the application directory permissions. Open the folder properties in Windows Explorer, go to the Security tab, and check which users or groups have Write or Modify permissions. Alternatively, run 'icacls "[installation_path]"' from an elevated command prompt to list all permission entries.
    Affected if Non-administrative users or the Users group have Write or Modify permissions on the DIAEnergie installation directory or its subdirectories, allowing them to place malicious DLL files.
  4. Confirm DLL search order behavior
    Monitor the application startup using Process Monitor from Sysinternals. Set a filter for Process Name equals DIAEnergie.exe and Operation equals CreateFile. Look for DLL load attempts with relative paths or from user-writable locations outside the system directories.
    Affected if The application loads DLLs using relative paths without fully qualifying the path, or loads DLLs from directories where unprivileged users have write access.

A system is affected if DIAEnergie version is below 1.8.02.004 AND the application directory permissions allow authenticated users to write files, enabling DLL hijacking for privilege escalation.

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

Update DIAEnergie to version 1.8.02.004 or later. Additionally, review and remediate file system permissions on the application directory to prevent unauthorized write access.

Recommended fix High confidence

1.8.02.004

  1. Back up all DIAEnergie configuration data and project files before proceeding with the upgrade
  2. Obtain DIAEnergie version 1.8.02.004 or later from the official Delta Electronics vendor distribution channel
  3. Uninstall the current vulnerable version of DIAEnergie following the vendor's standard uninstallation procedure
  4. Install the fixed version (1.8.02.004) following Delta Electronics installation documentation
  5. Verify that the installed version is 1.8.02.004 or later by checking the application version information
  6. Test that DIAEnergie operates normally after the upgrade

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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