dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-1375

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_slogHandler.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_slogHandler.ashx component of Delta Electronics DIAEnergie (versions prior to 1.8.02.004). The vulnerability allows unauthenticated attackers to inject arbitrary SQL queries, potentially leading to database exfiltration, modification, and in some configurations, OS command execution through database features.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later. If immediate patching is not possible, restrict network access to the affected DIAE_slogHandler.ashx endpoint and implement WAF rules to detect and block 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
    Locate the DIAEnergie installation directory on the system. Common paths include C:\inetpub\wwwroot\DIAEnergie or C:\Program Files\Delta Electronics\DIAEnergie. Check for the presence of the web application files (.aspx, .ashx handlers).
    Affected if DIAEnergie is installed and the web files are present on the server.
  2. Identify installed DIAEnergie version
    Locate the version information file or assembly metadata within the DIAEnergie installation directory. Version details may be in a version.txt file, the assembly info, or the application DLLs (typically in the bin folder). Compare the discovered version number against the vulnerable range of versions prior to 1.8.02.004.
    Affected if The installed version number is lower than 1.8.02.004.
  3. Verify vulnerable component exists
    Locate the DIAE_slogHandler.ashx file within the DIAEnergie web directory. This file handles logging operations and contains the blind SQL injection vulnerability.
    Affected if The file DIAE_slogHandler.ashx exists in the web application's handlers directory.
  4. Check component accessibility
    Verify the DIAE_slogHandler.ashx handler is accessible via HTTP/HTTPS from the network. Attempt a request to the endpoint (for example: http(s)://<server>/DIAEnergie/DIAE_slogHandler.ashx) using a web browser or curl command. A successful HTTP response (even an error) indicates the handler is reachable.
    Affected if The handler is accessible over the network without authentication requirements.

A user is affected if DIAEnergie is installed with a version lower than 1.8.02.004 and the DIAE_slogHandler.ashx component 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

Upgrade DIAEnergie to version 1.8.02.004 or later. If immediate patching is not possible, restrict network access to the affected DIAE_slogHandler.ashx endpoint and implement WAF rules to detect and block SQL injection patterns.

Recommended fix High confidence

1.8.02.004 or later

  1. 1. Identify all deployed instances of Delta Electronics DIAEnergie in the environment
  2. 2. Verify current installed version of DIAEnergie on each affected system
  3. 3. Obtain the fixed version 1.8.02.004 or later from Delta Electronics official distribution channels
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. Back up the current DIAEnergie installation including configuration files and database
  6. 6. Deploy version 1.8.02.004 or later to all affected systems
  7. 7. Verify the upgrade was successful and the application functions correctly
  8. 8. Confirm the vulnerability is remediated by checking that DIAE_slogHandler.ashx no longer accepts arbitrary SQL input
Caveat Review release notes for any configuration or behavioral changes between current version and 1.8.02.004

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
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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