CVE-2005-4021
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 · uneditedThe installer for Gallery 2.0 before 2.0.2 stores the install log under the web document root with insufficient access control, which allows remote attackers to obtain sensitive information.
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 confidenceThe Gallery 2.0 installer (versions before 2.0.2) stores installation log files within the web document root without proper access control restrictions, allowing remote attackers to directly request and view these logs to obtain sensitive installation-related information.
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.0= 2.0.1= 2.0_alpha1= 2.0_alpha2= 2.0_alpha3= 2.0_alpha4= 2.0_beta1= 2.0_beta2= 2.0_beta3= 2.0_rc1= 2.0_rc2CVSS 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 Gallery installation and versionCheck for the presence of Gallery 2.x installation by looking for the main Gallery PHP files or the version.php file within the web document root. Common paths include /gallery/ or the root directory. Look for a version file or check the admin interface for the installed version number.Affected if The installed version is any of: 2.0, 2.0.1, 2.0_alpha1, 2.0_alpha2, 2.0_alpha3, 2.0_alpha4, 2.0_beta1, 2.0_beta2, 2.0_beta3, 2.0_rc1, or 2.0_rc2 (versions before 2.0.2)
-
Locate installation log filesSearch the web document root for installation log files. Typical log file names may include install.log, setup.log, or similar files created during the installation process. Check common locations such as the gallery root directory or a logs subdirectory.Affected if Installation log files exist within the web document root directory
-
Verify web accessibility of log filesAttempt to directly access suspected log files via HTTP using a web browser or curl command. For example: http://your-site.com/gallery/install.log or http://your-site.com/gallery/logs/install.log.Affected if The log files return HTTP 200 status and display installation-related content when requested directly through the web server
You are affected if Gallery 2.0 through 2.0_rc2 is installed and installation log files are present within the web document root and accessible via HTTP 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 dataMove the install log directory outside the web document root or configure web server access controls to deny HTTP requests; alternatively, upgrade to Gallery 2.0.2 or later which addresses this issue.
- 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-2005-4021 — 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-2005-4021 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