dbcve.org
Device42Application

CVE-2021-41316

HIGH · 8.1 CVSS v3.1 Published 2021-09-17
Fix available
A fix is available. Upgrade to 17.05.01 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
The Device42 Main Appliance before 17.05.01 does not sanitize user input in its Nmap Discovery utility. An attacker (with permissions to add or edit jobs run by this utility) can inject an extra argument to overwrite arbitrary files as the root user on the Remote Collector.

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

Device42 Main Appliance versions before 17.05.01 fail to sanitize user input in the Nmap Discovery utility, allowing authenticated attackers with job management permissions to inject extra arguments into Nmap commands. This enables arbitrary file overwrite as root on Remote Collectors through argument injection.

MitigationUpgrade Device42 Main Appliance to version 17.05.01 or later which contains the fix for input sanitization. Limit permissions for the Nmap Discovery utility job management to trusted administrators only.

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
Device42Application
Affected:< 17.05.01

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Device42 Main Appliance version
    Access the Device42 administrative interface or check system information to find the currently installed version number of the Device42 Main Appliance
    Affected if The installed version is earlier than 17.05.01
  2. Confirm Nmap Discovery utility is in use
    Locate the Nmap Discovery utility or feature within the Device42 interface and verify it has been configured or used for network discovery jobs
    Affected if The Nmap Discovery utility is enabled or has been used to create discovery jobs
  3. Verify job management permissions
    Review user accounts and their assigned roles, specifically checking which users have permissions to create or manage discovery jobs
    Affected if Any user account with job management permissions exists in the system (especially non-administrator accounts)
  4. Check for configured Remote Collectors
    Examine the Device42 deployment configuration to determine if any Remote Collectors are connected to the Main Appliance
    Affected if Remote Collectors are deployed and connected to the Main Appliance

A user is affected if their Device42 Main Appliance version is below 17.05.01, the Nmap Discovery utility is in use, and Remote Collectors are configured, with the risk amplified if non-administrator users have job management permissions.

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

Upgrade Device42 Main Appliance to version 17.05.01 or later which contains the fix for input sanitization. Limit permissions for the Nmap Discovery utility job management to trusted administrators only.

Recommended fix High confidence

17.05.01 or later

  1. 1. Check current Device42 version in the admin UI under Settings > Appliance > Version or via CLI with 'd42 --version'
  2. 2. Backup the current Device42 appliance configuration and data following official backup procedures
  3. 3. Download Device42 version 17.05.01 or later from the official Device42 download portal (portal.device42.com)
  4. 4. Apply the upgrade following Device42's standard upgrade procedure - typically via the web UI (Settings > Appliance > Update) or ISO/image deployment
  5. 5. After upgrade completes, verify the new version is 17.05.01 or higher
  6. 6. Confirm the Nmap Discovery utility now properly sanitizes user input
Caveat Review Device42 release notes for 17.05.x for any configuration or feature changes that may require adjustment

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

Fix this in Device42 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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