CVE-2022-1367
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 Handler_TCV.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 confidenceA blind SQL injection vulnerability exists in Handler_TCV.ashx of Delta Electronics DIAEnergie (versions prior to 1.8.02.004). This allows unauthenticated attackers to inject arbitrary SQL queries, potentially leading to full database compromise and OS command execution.
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.
-
Confirm DIAEnergie installationSearch for the DIAEnergie application directory, typically found in C:\Program Files\Delta Electronics\DIAEnergie or inspect IIS/web server configurations for DIAEnergie web applicationsAffected if DIAEnergie is installed and running
-
Identify installed DIAEnergie versionCheck the version information in the application's About page, assembly metadata, or version file within the DIAEnergie installation directoryAffected if The installed version is any version prior to 1.8.02.004
-
Verify Handler_TCV.ashx exposureAttempt to access the Handler_TCV.ashx endpoint via HTTP (for example, http(s)://<hostname>/Handler_TCV.ashx) and confirm the handler responds or is reachableAffected if The handler is accessible without authentication
-
Check for unauthenticated SQL injection pointSend a crafted request to Handler_TCV.ashx with SQL syntax in parameter values (for example, adding a single quote or SQL true/false conditions) and observe application response behaviorAffected if The handler processes unauthenticated requests and reflects SQL syntax in database queries without proper parameterization
A user is affected if DIAEnergie versions prior to 1.8.02.004 are installed and the Handler_TCV.ashx endpoint is accessible without authentication, allowing blind SQL injection.
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
Update to version 1.8.02.004 or later; if unable to update, implement strict input validation and parameterized queries in the affected handler.
1.8.02.004 or later
- Obtain DIAEnergie version 1.8.02.004 or later from Delta Electronics (the vendor)
- Back up the current DIAEnergie installation and database before upgrading
- Install version 1.8.02.004 of DIAEnergie following the vendor's standard upgrade procedure
- Verify the upgrade was successful by checking the software version
- Confirm the Handler_TCV.ashx endpoint is no longer vulnerable to SQL injection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1367 — 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-1367 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