CVE-2022-1371
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 · uneditedDelta Electronics DIAEnergie (All versions prior to 1.8.02.004) has a blind SQL injection vulnerability exists in ReadRegf. 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 confidenceA blind SQL injection vulnerability exists in the ReadRegf component of Delta Electronics DIAEnergie (all versions prior to 1.8.02.004). Attackers can inject arbitrary SQL queries to retrieve/modify database contents and potentially execute system commands.
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< 1.8.02.004CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify DIAEnergie is installedInspect the system for DIAEnergie software installation (common locations include Program Files or application directories)Affected if DIAEnergie software is present on the system
-
Determine installed DIAEnergie versionLocate and read the version information for the DIAEnergie installation (typically accessible via the application's about dialog, installation metadata, or product documentation)Affected if The installed version number is lower than 1.8.02.004
-
Identify ReadRegf component exposureCheck if the ReadRegf component is exposed via web services, API endpoints, or network-accessible interfaces used by DIAEnergieAffected if The ReadRegf component is network-accessible without proper authentication controls
A system is affected if DIAEnergie is installed with any version prior to 1.8.02.004 and the ReadRegf component is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.8.02.004
Upgrade DIAEnergie to version 1.8.02.004 or later to remediate the SQL injection vulnerability.
1.8.02.004
- 1. Identify the current version of Delta Electronics DIAEnergie currently installed
- 2. Back up all DIAEnergie databases and configuration files before proceeding
- 3. Obtain the fixed version 1.8.02.004 or later from Delta Electronics official channels
- 4. Upgrade the DIAEnergie installation to version 1.8.02.004 or latest stable release
- 5. Verify the upgrade was successful by checking the new version number
- 6. Test that the ReadRegf functionality works correctly post-upgrade
- 7. Confirm the SQL injection vulnerability is remediated by reviewing system logs for any attempted injections
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1371 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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