CVE-2008-0136
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 · uneditedSnitz Forums 2000 3.4.05 allows remote attackers to obtain sensitive information via a direct request to forum/whereami.asp, which reveals the database path.
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 confidenceSnitz Forums 2000 version 3.4.05 contains a script at forum/whereami.asp that, when directly requested by a remote attacker, reveals the full filesystem path to the database. This information disclosure could aid attackers in planning further attacks by exposing system internals.
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= 3.4.05CVSS 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.
-
Confirm Snitz Forums 2000 is installedCheck for the presence of Snitz Forums 2000 by looking for common installation paths such as /forum/, /snitz/, or the presence of known Snitz files like forum.asp, members.asp, or config.asp in the web rootAffected if Snitz Forums 2000 is present on the server
-
Identify the installed versionLook for version information in the application - typically found in a config file, footer, or in the admin control panel. Common version file locations include info.asp, version.asp, or within the database configuration filesAffected if The installed version is 3.4.05
-
Check if whereami.asp existsLocate the file forum/whereami.asp (or /whereami.asp depending on installation) within the web directory structureAffected if The file whereami.asp exists in the forum directory
-
Test for path disclosure vulnerabilitySend an HTTP GET request directly to the whereami.asp file (e.g., http://target/forum/whereami.asp) and examine the response for filesystem path informationAffected if The response contains a full filesystem path, particularly a path to a database file (e.g., .mdb database path)
The server is affected if Snitz Forums 2000 version 3.4.05 is installed and the whereami.asp file is directly accessible, causing it to leak the database filesystem path in the response.
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 dataRemove or restrict access to the whereami.asp file in production environments, or configure the web server to prevent direct access to this administrative diagnostic script.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0136 — 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-2008-0136 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