CVE-2016-4814
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 · uneditedDirectory traversal vulnerability in kml2jsonp.php in Geospatial Information Authority of Japan (aka GSI) Old_GSI_Maps before January 2015 on Windows allows remote attackers to read arbitrary files via unspecified vectors.
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 confidenceDirectory traversal vulnerability in kml2jsonp.php in GSI Old_GSI_Maps allows remote attackers to read arbitrary files on Windows via path traversal in unspecified vectors. The vulnerability stems from insufficient input validation in the PHP file, enabling attackers to use '..' sequences to access files outside the web root.
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 dataall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Locate the GSI Old_GSI_Maps installationSearch your web server document root for the 'Old_GSI_Maps' directory or 'kml2jsonp.php' file. Common paths include /var/www/html/, C:\inetpub\wwwroot\, or your web application's root directory.Affected if The Old_GSI_Maps directory or kml2jsonp.php file exists on the server
-
Verify kml2jsonp.php is presentConfirm that kml2jsonp.php exists within the GSI Old_GSI_Maps installation folder. This is the specific file containing the directory traversal vulnerability.Affected if kml2jsonp.php is found in the application directory
-
Check if the file is web-accessibleAttempt to access kml2jsonp.php via HTTP/HTTPS through your web server (e.g., http://yourdomain/path/to/kml2jsonp.php). Verify the server responds to requests for this file.Affected if The file is accessible via HTTP/HTTPS and returns a response from the web server
-
Inspect the code for path traversal vulnerabilityOpen kml2jsonp.php in a text editor and search for file inclusion functions (include, require, file_get_contents, fopen, readfile) that use user-supplied input without proper sanitization. Look for parameters that could accept '..' sequences.Affected if The code uses unsanitized input in file operations or includes files based on request parameters without validating for '..' sequences
-
Test for directory traversal behaviorIf the code accepts a parameter (e.g., ?file= or ?kml=), attempt a benign test request with '..' patterns to observe if the application returns files outside the intended directory. On Windows, test with patterns like '..\\..\\windows\\win.ini' or '../' sequences.Affected if The application returns content from files outside the expected directory when '..' sequences are used in requests
If GSI Old_GSI_Maps is installed with web-accessible kml2jsonp.php that lacks input sanitization for path traversal, the environment is affected by this CVE.
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 GSI Old_GSI_Maps version released after January 2015, or implement strict input validation/sanitization on the kml2jsonp.php file to filter path traversal sequences (../) and restrict file access to intended directories.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4814 — 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-2016-4814 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