CVE-2022-3214
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 Industrial Automation's DIAEnergy, an industrial energy management system, is vulnerable to CWE-798, Use of Hard-coded Credentials. Versions prior to 1.9.03.009 have this vulnerability. Executable files could be uploaded to certain directories using hard-coded bearer authorization, allowing remote code execution.
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 confidenceDelta Industrial Automation's DIAEnergy versions prior to 1.9.03.009 contain hard-coded bearer authorization credentials that allow authenticated file uploads of executable content to specific directories, leading to remote code execution. The vulnerability is exploitable remotely with low complexity and no user interaction required.
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.9.03.009CVSS 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.
-
Identify DIAEnergy installation and versionLocate the DIAEnergy installation directory and check the version information file, or use the software's built-in 'About' or 'Help > Version' menu if accessible via the web interface. Common locations include C:\Program Files\Delta Industrial Automation\DIAEnergy or similar installation paths.Affected if The installed version is prior to 1.9.03.009
-
Verify the DIAEnergy web service is runningCheck if the DIAEnergy web interface is accessible and running. This can be done by accessing the application's URL (commonly on port 8080 or 80) or by checking running services on the host using 'netstat -ano' or Services.msc for a DIAEnergy service.Affected if The service is exposed and accessible over the network, making the hard-coded credentials reachable
-
Inspect configuration files for hard-coded credentialsExamine configuration files within the DIAEnergy installation directory, particularly files named config.xml, settings.xml, web.config, or similar configuration files in the conf or config subdirectories. Look for static bearer tokens, API keys, or authorization tokens that appear hard-coded rather than dynamically generated.Affected if Hard-coded bearer authorization credentials are present in configuration files
-
Check file upload functionality and permissionsIf accessible, navigate to the file upload feature in the web interface and verify if authenticated file uploads to directories that can contain executable content are possible. Review the application's logs for any recent file upload activity.Affected if The file upload feature is enabled and accessible without requiring dynamic, user-specific authentication
You are affected if DIAEnergy version is below 1.9.03.009 AND the application service is running with the hard-coded credentials still present in its configuration.
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.9.03.009
Update DIAEnergy to version 1.9.03.009 or later to replace hard-coded credentials with proper authentication mechanisms. Immediately rotate any credentials that may have been exposed and investigate logs for indicators of compromise.
1.9.03.009
- Identify the current version of DIAEnergy installed in the environment
- Contact Delta Industrial Automation to obtain the version 1.9.03.009 or later which contains the security fix
- Plan and schedule a maintenance window for the upgrade process
- Backup the current DIAEnergy configuration and data before proceeding with the upgrade
- Apply the upgrade to version 1.9.03.009 or newer following vendor documentation
- Verify that the hard-coded credentials have been removed or replaced with secure authentication mechanisms
- Test that the application functions correctly after the upgrade
- Confirm that the executable file upload vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3214 — 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-3214 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