CVE-2001-0892
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 · uneditedAcme Thttpd Secure Webserver before 2.22, with the chroot option enabled, allows remote attackers to view sensitive files under the document root (such as .htpasswd) via a GET request with a trailing /.
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 confidenceAcme Thttpd Secure Webserver versions prior to 2.22, when the chroot option is enabled, improperly handle GET requests containing a trailing slash (/), allowing remote attackers to access sensitive files within the document root (such as .htpasswd) that should be protected.
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.22CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Acme Thttpd installation and versionRun 'thttpd -v' or 'thttpd -h' to display the version information, or check the package manager for installed thttpd package versionAffected if Version displayed is 2.22 or lower (any version prior to 2.22)
-
Locate the thttpd configuration fileCommon locations include /etc/thttpd.conf, /etc/httpd.conf, or check the init script/process arguments for a custom config path using 'ps aux | grep thttpd'Affected if Configuration file exists and is in use by the running thttpd instance
-
Verify if chroot option is enabledOpen the configuration file and search for the 'chroot' directive or similar setting (such as 'chroot=yes' or 'chroot=1'), or check the thttpd command line arguments for chroot behaviorAffected if The chroot option is set to enabled (yes, true, or 1) in the configuration or startup arguments
-
Test for sensitive file exposure via trailing slashSend a GET request to the webserver with a trailing slash appended to the document root, such as 'GET /?/' or 'GET //' and check if files like .htpasswd or other normally protected files become accessibleAffected if Sensitive files that should be protected (like .htpasswd) are accessible via requests with trailing slashes when chroot is enabled
You are affected if you are running Acme Thttpd version 2.22 or lower AND have the chroot option enabled in your configuration, as this combination allows unauthorized access to protected files via trailing slash requests.
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 to Acme Thttpd Secure Webserver version 2.22 or later, or evaluate whether the chroot option is required for the deployment's security model and disable if unnecessary.
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0892 — 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-2001-0892 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