dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-1374

CRITICAL · 9.8 CVSS v3.1 Published 2022-05-02
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 exists in DIAE_unHandler.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 DIAE_unHandler.ashx handler of Delta Electronics DIAEnergie (all versions prior to 1.8.02.004). Attackers can inject arbitrary SQL queries through this endpoint, potentially enabling unauthorized database access and OS command execution on the underlying system.

MitigationApply vendor patch version 1.8.02.004 or later immediately. Until patched, restrict network access to the DIAEnergie interface and deploy WAF rules to detect 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. Confirm DIAEnergie installation
    Search for DIAEnergie installation directories (commonly in C:\Program Files\Delta Electronics\ or C:\inetpub\wwwroot\DIAEnergie) and check for the presence of DIAE_unHandler.ashx file in the web root
    Affected if DIAEnergie is installed and the DIAE_unHandler.ashx file exists in the web application directory
  2. Identify installed version
    Locate and open the version information file (typically version.txt, about page, or DLL version metadata in the DIAEnergie bin directory) and note the exact version number
    Affected if The installed version is lower than 1.8.02.004 (e.g., 1.8.01.001, 1.7.x, etc.)
  3. Verify handler is exposed
    Check the web.config file in the DIAEnergie web root for the DIAE_unHandler.ashx HttpHandler registration, or attempt a HEAD request to http(s)://<server>/DIAE_unHandler.ashx
    Affected if The handler is registered in web.config and responds to HTTP requests (returns 200 or 405 rather than 404)
  4. Check network exposure
    Review firewall rules, IIS bindings, and network ACLs to determine if the DIAEnergie web interface is accessible from untrusted networks
    Affected if The DIAEnergie web portal is accessible from the internet or untrusted internal networks without proper access controls

The environment is affected if DIAEnergie is installed with a version prior to 1.8.02.004 and the DIAE_unHandler.ashx endpoint is accessible 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 1.8.02.004 or later
Fixed in 1.8.02.004
Interim mitigation

Apply vendor patch version 1.8.02.004 or later immediately. Until patched, restrict network access to the DIAEnergie interface and deploy WAF rules to detect SQL injection patterns.

Recommended fix High confidence

1.8.02.004

  1. Upgrade DIAEnergie to version 1.8.02.004 or later to remediate the SQL injection vulnerability in DIAE_unHandler.ashx
  2. After upgrading, verify that the DIAE_unHandler.ashx endpoint is no longer vulnerable to SQL injection
  3. Test that all functionality works correctly after the upgrade
  4. Ensure the upgrade is performed in accordance with Delta Electronics' official upgrade documentation

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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