dbcve.org
DiaenergieApplication · Deltaww

CVE-2022-41133

HIGH · 8.8 CVSS v3.1 Published 2022-10-27
Fix available
A fix is available. Upgrade to 1.9.01.002 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
The affected product DIAEnergie (versions prior to v1.9.01.002) is vulnerable to a SQL injection that exists in GetDIAE_line_message_settingsListParameters. A low-privileged authenticated attacker could exploit this issue to inject arbitrary SQL queries.

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

DIAEnergie versions prior to v1.9.01.002 contain a SQL injection vulnerability in the GetDIAE_line_message_settingsListParameters function. A low-privileged authenticated attacker can exploit this to inject and execute arbitrary SQL queries, potentially allowing data exfiltration, modification, or in some scenarios, OS command execution via database features.

MitigationUpgrade DIAEnergie to version v1.9.01.002 or later. As an immediate compensating control, restrict network access to the application to minimize the attack surface and implement strict input validation/parameterized queries on the vulnerable endpoint until the patch is applied.

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

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 installed DIAEnergie version
    Check the application's About page, version information in the installation directory, or the login page footer which typically displays the version number. Compare this to the affected range: versions prior to 1.9.01.002 are vulnerable.
    Affected if The installed version is any build prior to 1.9.01.002
  2. Confirm the application is using database features
    Verify the DIAEnergie installation is connected to a backend database (such as SQL Server or MySQL) which is required for the SQL injection to have impact.
    Affected if The application is configured with a database backend that supports the vulnerable SQL queries
  3. Check for the vulnerable GetDIAE_line_message_settingsListParameters function
    Review application web logs or proxy captures for requests to the endpoint that invokes GetDIAE_line_message_settingsListParameters function, particularly GET/POST requests to message settings or related parameters.
    Affected if Requests to the vulnerable function are being processed by the application
  4. Verify authentication configuration
    Confirm whether the application's login mechanism is active and that low-privilege user accounts can be created or accessed, as the CVE requires an authenticated attacker.
    Affected if Low-privileged user authentication is enabled and accessible to untrusted users
  5. Review database logs for suspicious SQL activity
    Examine database transaction logs or audit logs for unusual or unexpected SQL queries, especially those containing UNION statements, DROP/DELETE commands, or xp_cmdshell attempts originating from the application user.
    Affected if Anomalous SQL queries appear in database logs indicating injection attempts

You are affected if DIAEnergie is installed at any version prior to 1.9.01.002, is accessible over the network to untrusted users, and has a database backend with authenticated access enabled.

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.01.002 or later
Fixed in 1.9.01.002
Interim mitigation

Upgrade DIAEnergie to version v1.9.01.002 or later. As an immediate compensating control, restrict network access to the application to minimize the attack surface and implement strict input validation/parameterized queries on the vulnerable endpoint until the patch is applied.

Recommended fix High confidence

DIAEnergie v1.9.01.002

  1. 1. Back up the current DIAEnergie installation and database before proceeding with any changes
  2. 2. Obtain the fixed version v1.9.01.002 from the vendor (DIAenergie)
  3. 3. Test the upgrade in a non-production environment to verify compatibility with your existing setup
  4. 4. Apply the upgrade to production systems following vendor documentation
  5. 5. Verify the vulnerability is resolved by testing the GetDIAE_line_message_settingsListParameters endpoint
  6. 6. Confirm normal operation of DIAEnergie functionality post-upgrade

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 / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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