Automatic Device ManagementApplication · Invigo

CVE-2020-10579

HIGH · 7.5 CVSS v3.1 Published 2021-03-25
Fix available
A fix is available. Upgrade to after 5.0 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
A directory traversal on the /admin/sysmon.php script of Invigo Automatic Device Management (ADM) through 5.0 allows remote attackers to list the content of arbitrary server directories accessible to the user running the application.

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

A directory traversal vulnerability in /admin/sysmon.php of Invigo Automatic Device Management (ADM) through version 5.0 allows remote attackers to access directory listings of arbitrary server paths accessible to the web server process user, by manipulating path parameters with traversal sequences (e.g., ../../).

MitigationImplement strict input validation and path normalization in sysmon.php to restrict file path parameters to whitelisted directories and prevent traversal sequences; also ensure the web server runs with minimal filesystem privileges.

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
Automatic Device ManagementApplication
Affected:<= 5.0

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. Verify Invigo ADM installation and version
    Check if Invigo Automatic Device Management is installed and determine the installed version by examining application files, headers, or administrative interfaces. Compare against the affected range: <= 5.0
    Affected if Installed version is 5.0 or lower, or version cannot be determined but the product is present
  2. Confirm sysmon.php exists in /admin/
    Locate the file sysmon.php within the /admin/ directory of the web application root. This is the vulnerable component.
    Affected if The file /admin/sysmon.php exists in the web application directory
  3. Identify web server user filesystem access
    Determine which user the web server process runs as, and check what directories that user has read access to on the system
    Affected if The web server user has access to sensitive directories beyond the web root
  4. Test path parameter for traversal vulnerability
    Send an HTTP request to /admin/sysmon.php with a manipulated path parameter containing traversal sequences such as ../../ or ../../../../etc, observing whether directory listings are returned or file contents are exposed
    Affected if The path parameter accepts and processes ../ sequences and returns directory listings or file contents outside the intended directory
  5. Check if directory listing feature is enabled
    Examine the sysmon.php source code or behavior to confirm that it returns directory listings when given a valid path, making traversal meaningful
    Affected if The script returns directory index/listing output for provided paths

A defender is affected if Invigo ADM version 5.0 or lower is installed, the /admin/sysmon.php file exists, and the path parameter in that script accepts directory traversal sequences to list arbitrary directories accessible to the web server user.

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.

From vendor data
Upgrade available Upgrade to a release after 5.0
Interim mitigation

Implement strict input validation and path normalization in sysmon.php to restrict file path parameters to whitelisted directories and prevent traversal sequences; also ensure the web server runs with minimal filesystem privileges.

Fix this in Automatic Device Management Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10579 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10579 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