dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-1377

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_rltHandler.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_rltHandler.ashx handler of Delta Electronics DIAEnergie (all versions prior to 1.8.02.004). Attackers can inject arbitrary SQL queries through this endpoint, potentially allowing database content retrieval/modification and OS command execution.

MitigationUpgrade DIAEnergie to version 1.8.02.004 or later; if immediate upgrade is not feasible, implement input validation, parameterized queries, and network segmentation to reduce exploitability.

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 web application directory on the server. Check for the presence of the 'DIAE_rltHandler.ashx' file within the web root (typically under inetpub or the application's deployed folder).
    Affected if The file DIAE_rltHandler.ashx exists in the web application directory.
  2. Identify installed version
    Locate version information within the DIAEnergie installation. Check the assembly version of the main application DLLs, or look for a version.txt/version.info file in the application root directory. Alternatively, access the application's 'About' or 'System Information' page if available via the web interface.
    Affected if The installed version number cannot be determined OR the identified version is below 1.8.02.004.
  3. Verify handler is accessible
    Attempt to access the vulnerable endpoint via HTTP request: http(s)://<hostname>/Handler/DIAE_rltHandler.ashx. A successful connection (even if returning an error) indicates the handler is exposed.
    Affected if The handler responds to HTTP requests, indicating it is exposed and potentially exploitable.
  4. Check network exposure
    Review firewall rules, IIS bindings, or network ACLs to determine if the DIAEnergie web interface (specifically the Handler directory) is accessible from untrusted networks or the internet.
    Affected if The handler is accessible from networks outside the trusted internal environment.

A user is affected if DIAEnergie with the vulnerable handler is installed, the installed version is below 1.8.02.004, and the handler is network-accessible.

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 upgrade is not feasible, implement input validation, parameterized queries, and network segmentation to reduce exploitability.

Recommended fix High confidence

1.8.02.004

  1. Backup the current DIAEnergie installation and database before proceeding with the upgrade.
  2. Obtain DIAEnergie version 1.8.02.004 or later from Delta Electronics official distribution channels.
  3. Stop the DIAEnergie web application services.
  4. Install version 1.8.02.004 following Delta Electronics upgrade documentation.
  5. Restart the DIAEnergie services.
  6. Verify the upgrade was successful by checking the DIAEnergie version number.
  7. Confirm the DIAE_rltHandler.ashx endpoint is no longer vulnerable by testing or reviewing vendor release notes.

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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