CVE-2022-41572
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 · uneditedAn issue was discovered in EyesOfNetwork (EON) through 5.3.11. Privilege escalation can be accomplished on the server because nmap can be run as root. The attacker achieves total control over the server.
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 confidenceA privilege escalation vulnerability in EyesOfNetwork (EON) through version 5.3.11 allows attackers to achieve full server control because the nmap utility can be executed with root privileges. An attacker who can trigger nmap execution gains the ability to run commands as root, leading to complete compromise of the affected system.
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<= 5.3-11CVSS 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.
-
Verify EyesOfNetwork installation and versionCheck if EyesOfNetwork is installed by looking for its typical installation directories (e.g., /opt/eonweb, /usr/local/eonweb) or by querying the package manager if it was installed via packages. Identify the installed version by examining version files in the installation directory or running 'rpm -q' / 'dpkg -l' for eyesofnetwork packages.Affected if The installed version is 5.3-11 or any version lower than 5.3-11.
-
Locate the nmap binaryFind the nmap binary on the system using 'which nmap' or 'find /usr -name nmap -type f 2>/dev/null'. Note the full path to the binary.Affected if The nmap binary exists on the system and is accessible to the application user.
-
Inspect sudo rules for nmapExamine the sudoers configuration for nmap by checking /etc/sudoers and files in /etc/sudoers.d/. Look for entries that allow nmap to run with root privileges (e.g., 'ALL ALL=NOPASSWD: /usr/bin/nmap' or similar patterns). Use 'sudo -l -U <username>' for the application user if applicable to see their sudo privileges.Affected if There exists a sudo rule that permits the application or limited user to run nmap with elevated (root) privileges without a password or with unrestricted options.
-
Test nmap execution with elevated privilegesAs the limited user account that would be exploited, attempt to run 'sudo nmap --version' or 'sudo nmap -h' to confirm whether nmap can be executed with root privileges.Affected if The limited user can execute nmap with sudo and gains root-level capabilities.
A user is affected if they have EyesOfNetwork version 5.3-11 or lower installed AND there exists a sudo configuration that allows a limited user to run nmap with root privileges.
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.
From vendor dataRestrict nmap execution to non-privileged users by reviewing and tightening file permissions, sudo rules, or application configurations that allow nmap to run as root; consider upgrading to a patched version if available beyond 5.3.11.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41572 — 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-41572 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