dbcve.org
CmdbApplication · Device42

CVE-2022-1401

HIGH · 7.5 CVSS v3.1 Published 2022-08-17
Fix available
A fix is available. Upgrade to 18.01.00 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Improper Access Control vulnerability in the /Exago/WrImageResource.adx route as used in Device42 Asset Management Appliance allows an unauthenticated attacker to read sensitive server files with root permissions. 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 · high confidence

Improper Access Control vulnerability in the /Exago/WrImageResource.adx route of Device42 CMDB allows unauthenticated attackers to read sensitive server files with root permissions due to missing authentication checks on the endpoint.

MitigationUpgrade Device42 CMDB to version 18.01.00 or later to obtain the patched version, and verify the /Exago/WrImageResource.adx endpoint now requires proper authentication before granting file access.

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
CmdbApplication
Affected:< 18.01.00

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 Device42 CMDB version
    Locate the version information in the Device42 web interface (typically in Help > About or the footer), or check the installation directory for a version file. Compare the installed version number against the affected range.
    Affected if The installed version is any release prior to 18.01.00 (e.g., 17.x.x, 16.x.x, etc.)
  2. Confirm endpoint exposure
    Verify that the /Exago/WrImageResource.adx endpoint is reachable on the Device42 server. This is typically accessible at http(s)://<device42_host>/Exago/WrImageResource.adx.
    Affected if The endpoint responds to HTTP/HTTPS requests, indicating it is exposed.
  3. Test for unauthenticated access
    Send an HTTP GET request to the /Exago/WrImageResource.adx endpoint without providing any authentication credentials (no session cookie, token, or Basic Auth). Observe whether the server returns file contents or allows file path traversal.
    Affected if The endpoint returns file data or accepts path parameters without requiring authentication, confirming the vulnerability is present.

A user is affected if their Device42 CMDB version is below 18.01.00 AND the /Exago/WrImageResource.adx endpoint is exposed and accessible without authentication credentials.

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 18.01.00 or later
Fixed in 18.01.00
Interim mitigation

Upgrade Device42 CMDB to version 18.01.00 or later to obtain the patched version, and verify the /Exago/WrImageResource.adx endpoint now requires proper authentication before granting file access.

Recommended fix High confidence

18.01.00

  1. 1. Identify current Device42 CMDB version by checking the appliance administration interface or running: sudo /opt/device42/cmdb/bin/d42cmd -v
  2. 2. If version is below 18.01.00, plan for upgrade to version 18.01.00 or later
  3. 3. Create a complete backup of the Device42 appliance including configuration and database
  4. 4. Review Device42 upgrade documentation for your current version to ensure compatibility
  5. 5. Schedule maintenance window as upgrade may require system restart
  6. 6. Perform the upgrade following vendor-approved upgrade procedures
  7. 7. After upgrade, verify the /Exago/WrImageResource.adx route now requires proper authentication
  8. 8. Confirm sensitive server files are no longer accessible without authorization
Caveat Review release notes for 18.01.00 for any configuration changes or migration requirements that may affect your setup

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cmdb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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