CVE-2022-27903
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 OS Command Injection vulnerability in the configuration parser of Eve-NG Professional through 4.0.1-65 and Eve-NG Community through 2.0.3-112 allows a remote authenticated attacker to execute commands as root by editing virtualization command parameters of imported UNL files.
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 confidenceAn OS Command Injection vulnerability in Eve-NG's configuration parser allows authenticated users to execute arbitrary commands as root by manipulating virtualization command parameters within imported UNL (Unified Networking Lab) files. The vulnerability exists in how the application processes and parses configuration settings from these files.
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<= 2.0.3-112<= 4.0.1-65CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Eve-NG installationCheck if Eve-NG is running in your environment by reviewing your inventory, deployed virtual machines, or network services on ports 80/443.Affected if Eve-NG is present in your environment
-
Determine installed Eve-NG versionAccess the Eve-NG web interface and navigate to the about or system information page to view the installed version number, or check via CLI if you have shell access.Affected if The installed version is 2.0.3-112 or lower for Community edition, or 4.0.1-65 or lower for Professional edition
-
Verify UNL file import functionalityCheck if the UNL (Unified Networking Lab) import feature is available and enabled in the Eve-NG web interface under the template or lab import sections.Affected if UNL file import functionality is accessible and enabled
-
Review user access controlsExamine the list of users with access to the Eve-NG management interface and confirm whether any untrusted or unauthorized accounts exist.Affected if Untrusted or unauthorized users have authenticated access to Eve-NG
-
Inspect for signs of exploitationReview system logs (typically in /var/log or via the Eve-NG logging system) for any anomalous commands, unexpected script executions, or suspicious activity related to lab or template imports.Affected if Suspicious commands or unexpected root-level executions appear in logs around the time of UNL file imports
Your environment is affected if Eve-NG is running with a version at or below 2.0.3-112 (Community) or 4.0.1-65 (Professional), the UNL import feature is enabled, and untrusted users have authenticated access to the system.
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 access to Eve-NG management interfaces to trusted, authorized users only. Apply vendor patches when released for Eve-NG Professional 4.0.1-65 and Community 2.0.3-112.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27903 — 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-27903 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