CVE-2007-6361
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 · uneditedGekko 0.8.2 and earlier stores sensitive information under the web root with possibly insufficient access control, which might allow remote attackers to read certain files under temp/, as demonstrated by a log file that records the titles of blog entries. NOTE: access to temp/ is blocked by .htaccess in most deployments that use Apache HTTP Server.
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 confidenceGekko 0.8.2 and earlier stores sensitive information (specifically log files recording blog entry titles) in the temp/ directory under the web root with insufficient access controls, potentially allowing remote attackers to directly read these files via HTTP requests.
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.8.2CVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 Gekko installation versionLocate the Gekko installation directory and check for a version file or any file containing version information (such as version.php, about.php, or a README file). Alternatively, check the HTTP banner or admin interface if accessible.Affected if Installed version is 0.8.2 or earlier
-
Verify temp directory exists under web rootLocate the 'temp' or 'tmp' directory within the web-accessible portion of the Gekko installation. Common paths include /temp/ or /tmp/ at the root of the web application.Affected if The temp/ directory exists within the web root structure
-
Confirm temp directory is HTTP-accessibleAttempt to access the temp/ directory via HTTP using a web browser or curl command (e.g., curl -I http://target/temp/). Check if the directory listing or any files are returned without authentication or blocking.Affected if HTTP requests to the temp/ directory return directory contents or file data (not a 403 Forbidden or 404 Not Found)
-
Inspect temp directory for log filesIf accessible via HTTP, enumerate files within the temp/ directory. If not directly accessible, use local file system access to list files in temp/ and check for log files, particularly those containing blog entry titles.Affected if Log files containing blog entry titles or other sensitive data are present in the temp/ directory
The environment is affected if Gekko version 0.8.2 or earlier is installed AND the temp/ directory is accessible via HTTP requests, allowing remote attackers to read sensitive log files.
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 dataEnsure temp/ directory is not accessible from the web (already protected by .htaccess in Apache deployments); ideally move sensitive files outside the web root entirely and apply proper file permissions.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6361 — 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-2007-6361 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