CVE-2011-3749
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 · uneditedka-Map 1.0-20070205 allows remote attackers to obtain sensitive information via a direct request to a .php file, which reveals the installation path in an error message, as demonstrated by test.php and certain other 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 · moderate confidenceka-Map 1.0-20070205 contains PHP files (such as test.php) that, when accessed directly, output verbose error messages revealing the server's installation path. This path disclosure can aid attackers in reconnaissance for subsequent attacks.
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= 1.0-20070205CVSS 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 ka-Map installationSearch the web server document root for ka-Map directory structure or files containing 'ka-Map' or 'kamap' in their metadata. Check common web directories (htdocs, www, html, web) for ka-Map-related folders.Affected if ka-Map version 1.0-20070205 is found installed on the server
-
Locate test.php fileSearch for a file named test.php within the ka-Map installation directory, particularly in the main ka-Map folder or any subdirectories.Affected if test.php file exists in the ka-Map installation
-
Test direct access to test.phpUsing a web browser or curl, make an HTTP GET request directly to the test.php file (e.g., http://[hostname]/[ka-map-path]/test.php). Observe the response for any error messages or output.Affected if The response contains verbose error messages, stack traces, or explicitly reveals the server's filesystem installation path
-
Check for similar diagnostic filesSearch for other PHP files in the ka-Map directory that may serve diagnostic or testing purposes (e.g., phpinfo.php, debug.php, or any file with 'test' or 'debug' in the name).Affected if Additional diagnostic PHP files are present and accessible, or return path information when accessed directly
-
Verify error handling configurationExamine the PHP configuration (php.ini) or ka-Map configuration files for error reporting settings. Check if display_errors is enabled.Affected if PHP display_errors is set to On, allowing verbose error messages to be shown to remote users
A server is affected if ka-Map version 1.0-20070205 is installed and the test.php (or similar diagnostic PHP files) are directly accessible via HTTP and reveal the server's filesystem path in error output.
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 diagnostic and test PHP files (test.php and similar) from production deployments, and implement custom error handling to prevent path disclosure in error messages.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3749 — 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-2011-3749 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