dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
EyesofnetworkApplication

CVE-2020-8655

HIGH · 7.8 CVSS v3.1 Published 2020-02-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
In the wild High EPSS Public exploit No privileges

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
An issue was discovered in EyesOfNetwork 5.3. The sudoers configuration is prone to a privilege escalation vulnerability, allowing the apache user to run arbitrary commands as root via a crafted NSE script for nmap 7.

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

In EyesOfNetwork 5.3, the sudoers configuration incorrectly grants the apache user permission to execute nmap with root privileges. By leveraging nmap's NSE (Nmap Scripting Engine) functionality through a crafted script, an attacker can achieve arbitrary command execution as root, resulting in complete system compromise.

MitigationRemove or properly restrict the apache user's sudo permissions for nmap in the sudoers configuration file (/etc/sudoers or in /etc/sudoers.d/). Review whether nmap functionality is actually required by the apache user and implement least-privilege access controls.

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
EyesofnetworkApplication
Affected:= 5.3-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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Identify EyesOfNetwork installation and version
    Check for EyesOfNetwork by looking for /opt/eonweb/ or /usr/local/eyesofnetwork/, and find version files such as /opt/eonweb/include/version.php or /etc/eyesofnetwork/version
    Affected if The installed version is exactly 5.3-0
  2. Locate sudoers configuration files
    Examine /etc/sudoers and any files in /etc/sudoers.d/ directory for entries concerning the apache user
    Affected if A sudoers entry exists for the apache user that grants sudo privileges
  3. Inspect nmap-related sudo entries
    Search sudoers files for any rule allowing the apache user to run nmap with elevated privileges using grep -i 'apache.*nmap' or grep -i 'nmap.*apache'
    Affected if The apache user has sudo permission to execute nmap as root
  4. Check for broad command execution privileges
    Look for sudoers rules allowing apache to run any command or script via nmap --script or similar patterns with sudo
    Affected if The apache user can execute arbitrary commands through nmap or related sudo rules

A user is affected if running EyesOfNetwork version 5.3-0 and the sudoers configuration grants the apache user sudo privileges for nmap or similar tools that enable arbitrary command execution.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or properly restrict the apache user's sudo permissions for nmap in the sudoers configuration file (/etc/sudoers or in /etc/sudoers.d/). Review whether nmap functionality is actually required by the apache user and implement least-privilege access controls.

Recommended fix Moderate confidence
  1. Locate the sudoers configuration file, typically at /etc/sudoers or in /etc/sudoers.d/
  2. Find the line granting the apache user permission to run nmap as root (e.g., 'apache ALL=(root) NOPASSWD: /usr/bin/nmap')
  3. Remove or comment out this sudoers entry to revoke the apache user's ability to run nmap with elevated privileges
  4. Validate the sudoers configuration using 'visudo' to check for syntax errors
  5. Restart the Apache service if needed for changes to take effect
Caveat Removing this sudoers rule will prevent the EyesOfNetwork web interface from using nmap with root privileges, which may impact some network discovery or monitoring features that rely on nmap scanning

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

Fix this in Eyesofnetwork Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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-2020-8655 — 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-2020-8655 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