dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-43457

HIGH · 8.8 CVSS v3.1 Published 2022-11-17
Fix available
A fix is available. Upgrade to 1.9.02.001 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
SQL Injection in HandlerPage_KID.ashx in Delta Electronics DIAEnergie versions prior to v1.9.02.001 allows an attacker to inject SQL queries via Network

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

SQL injection vulnerability in HandlerPage_KID.ashx of Delta Electronics DIAEnergie allows remote attackers to inject malicious SQL queries via network. The vulnerability affects versions prior to v1.9.02.001.

MitigationUpgrade DIAEnergie to version v1.9.02.001 or later. If immediate patching is not feasible, implement input validation, parameterized queries, and consider deploying a WAF as a compensating control.

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.9.02.001

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

CVSS:3.1/AV:N/AC:L/PR:L/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 'DIAEnergie' folder in common installation paths such as C:\Program Files\Delta Electronics\ or C:\inetpub\wwwroot\. Check if HandlerPage_KID.ashx exists within the web application's handlers or scripts folder.
    Affected if DIAEnergie software is present on the system with the vulnerable handler file accessible via web server.
  2. Identify DIAEnergie version
    Check the version of the installed DIAEnergie. Common methods: right-click the executable (DIAEnergie.exe) and select Properties > Details tab; examine version info in the installation folder; check the application's About or Help section; or inspect version metadata in DLLs within the installation directory.
    Affected if The installed version number is lower than 1.9.02.001 (e.g., 1.9.01.002, 1.8.x, etc.).
  3. Verify HandlerPage_KID.ashx is exposed
    If DIAEnergie is hosted on IIS or another web server, confirm that the HandlerPage_KID.ashx endpoint is accessible. Access the URL directly in a browser (e.g., http://hostname/DIAEnergie/HandlerPage_KID.ashx) or check IIS handler mappings configuration.
    Affected if The handler is accessible and accepts user-supplied input without parameterized query protection.
  4. Confirm web server configuration
    Review the web.config file in the DIAEnergie web directory for custom handler registrations. Check IIS manager for Handler Mappings associated with .ashx extensions.
    Affected if HandlerPage_KID.ashx is registered and enabled as an HTTP handler in the web server configuration.

A system is affected if DIAEnergie is installed with HandlerPage_KID.ashx accessible and the installed version is below 1.9.02.001.

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.9.02.001 or later
Fixed in 1.9.02.001
Interim mitigation

Upgrade DIAEnergie to version v1.9.02.001 or later. If immediate patching is not feasible, implement input validation, parameterized queries, and consider deploying a WAF as a compensating control.

Recommended fix Moderate confidence

DIAEnergie v1.9.02.001

  1. 1. Identify the current version of Delta Electronics DIAEnergie installed in your environment
  2. 2. If the installed version is prior to v1.9.02.001, obtain the v1.9.02.001 or later release from Delta Electronics official channels
  3. 3. Review all upgrade documentation and release notes provided by Delta Electronics
  4. 4. Create a full backup of the DIAEnergie system, including configuration files and databases
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade to production systems following Delta Electronics' recommended upgrade procedure
  7. 7. Verify the upgrade was successful and the DIAEnergie application is functioning normally
  8. 8. Confirm the SQL injection vulnerability in HandlerPage_KID.ashx is no longer present

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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