dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-43447

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 AM_EBillAnalysis.aspx 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 · moderate confidence

SQL injection vulnerability in the AM_EBillAnalysis.aspx page of Delta Electronics DIAEnergie (versions prior to v1.9.02.001) allows remote attackers to inject arbitrary SQL queries via unsanitized input parameters. This high-severity flaw can lead to unauthorized database access, data exfiltration, or potential command execution depending on database configuration.

MitigationUpgrade DIAEnergie to version v1.9.02.001 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to filter malicious SQL injection payloads and restrict network access to the affected interface.

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. Identify DIAEnergie installation and version
    Locate the DIAEnergie installation directory and check the version information file, or access the application's About/Version page if available. Common locations include the installation folder under Program Files or the web application's root directory.
    Affected if The installed version is below 1.9.02.001
  2. Confirm AM_EBillAnalysis.aspx page exists
    Check if the AM_EBillAnalysis.aspx file exists in the web application's directory structure, typically under the web root or a subdirectory containing the application's aspx pages.
    Affected if The AM_EBillAnalysis.aspx file is present in the deployment
  3. Verify the vulnerable endpoint is accessible
    Attempt to access the AM_EBillAnalysis.aspx page via HTTP/HTTPS request to determine if the page is exposed on the network. Check web server logs for requests to this endpoint.
    Affected if The page is accessible over the network without authentication restrictions
  4. Check for unsanitized parameter handling
    Review the application's request handling logs or intercept a request to AM_EBillAnalysis.aspx to observe how input parameters are processed. Look for parameters that are passed directly to database queries without visible sanitization.
    Affected if The page accepts user-supplied input parameters that are not validated or parameterized in the application code

A user is affected if DIAEnergie version is below 1.9.02.001 AND the AM_EBillAnalysis.aspx page is accessible and processes user input without proper SQL injection protection.

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 possible, implement web application firewall (WAF) rules to filter malicious SQL injection payloads and restrict network access to the affected interface.

Recommended fix High confidence

v1.9.02.001

  1. Identify all deployments of Delta Electronics DIAEnergie versions prior to v1.9.02.001 in the environment
  2. Create a complete backup of the current DIAEnergie installation and its database
  3. Obtain the fixed version v1.9.02.001 from Delta Electronics official support channels (https://www.delta.com.tw or through authorized resellers)
  4. Deploy the fixed version in a staging or test environment to verify compatibility with existing systems and configurations
  5. Apply the upgrade to production systems after successful testing
  6. Verify that the AM_EBillAnalysis.aspx page no longer accepts SQL injection payloads and the vulnerability is remediated
Caveat Review Delta Electronics release notes for v1.9.02.001 to check for any configuration or data migration requirements before upgrading

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

Fix this in Diaenergie Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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