CVE-2022-1400
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 · uneditedUse of Hard-coded Cryptographic Key vulnerability in the WebReportsApi.dll of Exago Web Reports, as used in the Device42 Asset Management Appliance, allows an attacker to leak session IDs and elevate privileges. This issue affects: Device42 CMDB versions prior to 18.01.00.
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 confidenceA hard-coded cryptographic key embedded in WebReportsApi.dll of Exago Web Reports (used in Device42 Asset Management Appliance) allows attackers to decrypt or forge session IDs, leading to unauthorized access and privilege escalation. The vulnerability exists in Device42 CMDB versions prior to 18.01.00.
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< 18.01.00CVSS 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 Device42 CMDB installationIdentify whether Device42 CMDB is deployed in your environment by reviewing installed software, services, or documentation of managed assets.Affected if Device42 CMDB is present in your environment
-
Determine installed Device42 CMDB versionLocate the version information for your Device42 CMDB installation through the web interface, configuration files, or system inventory records.Affected if Version cannot be determined or shows as unknown
-
Compare version against vulnerable rangeReview the detected version number and compare it to the affected range: versions prior to 18.01.00.Affected if Installed version is below 18.01.00
-
Verify vulnerable component presenceIf accessible, inspect the WebReportsApi.dll file included with the Exago Web Reports integration for the presence of embedded cryptographic material.Affected if The DLL contains a hard-coded key (confirms the vulnerability is present)
-
Audit for indicators of exploitationReview access logs, authentication records, and session data for unauthorized access patterns or privilege escalation attempts that may indicate exploitation of forged session IDs.Affected if Suspicious session activity or unauthorized administrative access is observed
Your environment is affected if Device42 CMDB is installed with a version lower than 18.01.00, as this version range contains the hard-coded cryptographic key in WebReportsApi.dll.
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 · scoped18.01.00
Upgrade Device42 CMDB to version 18.01.00 or later to replace the hard-coded key. Additionally, rotate all active sessions and review access logs for signs of exploitation.
18.01.00
- Upgrade Device42 CMDB to version 18.01.00 or later to resolve the hard-coded cryptographic key vulnerability in WebReportsApi.dll
- Verify the upgrade by checking the Device42 CMDB version after installation
- After upgrade, review session management and user privileges to ensure no unauthorized access occurred
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-1400 — 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-1400 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