dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-0923

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to 1.8.02.004 or later.
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
Delta Electronics DIAEnergie (All versions prior to 1.8.02.004) has a blind SQL injection vulnerability that exists in HandlerDialog_KID.ashx. This allows an attacker to inject arbitrary SQL queries, retrieve and modify database contents, and execute system commands.

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 blind SQL injection vulnerability exists in the HandlerDialog_KID.ashx component of Delta Electronics DIAEnergie (versions prior to 1.8.02.004). The flaw allows unauthenticated attackers to inject arbitrary SQL queries, potentially leading to database exfiltration, modification, and OS command execution.

MitigationUpdate DIAEnergie to version 1.8.02.004 or later. Until patched, restrict network access to the affected handler and implement WAF rules for SQL injection patterns.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 DIAEnergie installation directory
    Search for the DIAEnergie installation folder, typically found in C:\Program Files\Delta Electronics\DIAEnergie or similar paths. Check for the presence of HandlerDialog_KID.ashx within the web handler directories.
    Affected if The HandlerDialog_KID.ashx file exists in the installation
  2. Identify installed DIAEnergie version
    Open the DIAEnergie installation folder and locate version information. Common locations include a version.txt file, assembly information within DLL files, or the application itself may display the version on startup or in About/Help menus.
    Affected if The installed version is lower than 1.8.02.004 (versions like 1.8.01.x, 1.8.00.x, 1.7.x, etc.)
  3. Verify HandlerDialog_KID.ashx is web-accessible
    Check the web server configuration (IIS or built-in web server) to confirm HandlerDialog_KID.ashx is exposed via HTTP/HTTPS. Attempt a HEAD request to the handler URL pattern: /HandlerDialog_KID.ashx
    Affected if The handler is accessible over the network without authentication

A system is affected if DIAEnergie is installed with a version prior to 1.8.02.004 and the HandlerDialog_KID.ashx component is web-accessible, allowing unauthenticated SQL injection.

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. Until patched, restrict network access to the affected handler and implement WAF rules for SQL injection patterns.

Recommended fix High confidence

1.8.02.004

  1. 1. Identify the current DIAEnergie version installed in your environment
  2. 2. Confirm the version is prior to 1.8.02.004 (vulnerable)
  3. 3. Contact Delta Electronics official support or download portal to obtain version 1.8.02.004 or later
  4. 4. Perform a full backup of the DIAEnergie application, configuration files, and database
  5. 5. Test the upgrade in a non-production environment before deploying to production
  6. 6. Apply the upgrade following Delta Electronics' official upgrade documentation
  7. 7. Verify the HandlerDialog_KID.ashx handler is updated and no longer accepts SQL injection
  8. 8. Confirm the application functions normally post-upgrade

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation8.0 h
  • Implementation8.0 h
  • Testing16.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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