CVE-2002-2201
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 · uneditedThe Printer Administration module for Webmin 0.990 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the printer name.
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 confidenceRemote command injection vulnerability in Webmin's Printer Administration module (versions 0.990 and earlier). Attackers can execute arbitrary OS commands by embedding shell metacharacters into the printer name parameter, leading to complete system compromise.
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<= 0.99CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Webmin installation and versionCheck the Webmin version file typically located at /etc/webmin/version, or access the Webmin web interface and look for the version number in the footer or 'System Information' page.Affected if The installed version is 0.990 or earlier, or any version numbered 0.99 or lower.
-
Verify the Printer Administration module is presentCheck for the existence of the printers module directory at /etc/webmin/printers/ or /var/webmin/printers/, or log into Webmin and look for 'Printer Administration' or ' printers' in the available modules list.Affected if The Printer Administration module is installed and visible in Webmin.
-
Confirm the Printer module is enabledCheck if the printers module is listed as active in /etc/webmin/config or /etc/webmin/printers/config, or verify in Webmin's module configuration that printers is not disabled.Affected if The Printer Administration module is enabled and accessible to users.
-
Assess network exposure of WebminDetermine if the Webmin web interface (default port 10000) is listening on a publicly accessible IP address or is reachable from untrusted networks. Check listening services with 'netstat -tlnp | grep 10000' or review firewall rules.Affected if Webmin is reachable from untrusted networks and the Printer module is enabled.
You are affected if Webmin version 0.990 or earlier is installed, the Printer Administration module is enabled, and the Webmin interface is network-accessible to untrusted users.
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 dataUpgrade Webmin to a version newer than 0.990, or apply vendor-released patches for this vulnerability. If immediate patching is not feasible, disable the Printer Administration module and restrict Webmin access to trusted networks.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2201 — 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-2002-2201 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