CVE-2009-1085
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 · uneditedPiwik 0.2.32 and earlier stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain the API key and other sensitive information via a direct request for misc/cron/archive.sh.
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 confidencePiwik 0.2.32 and earlier stores the misc/cron/archive.sh script (containing API keys and other sensitive data) in a web-accessible directory without proper access controls, allowing unauthenticated remote attackers to directly request and download this file to obtain sensitive credentials.
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.2.32= 0.2.25= 0.2.26= 0.2.27= 0.2.28= 0.2.29= 0.2.30= 0.2.31CVSS 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.
-
Verify if misc/cron/archive.sh exists in the web rootCheck the filesystem for the presence of misc/cron/archive.sh within the web document root directoryAffected if The file exists in a web-accessible location (inside the document root)
-
Confirm the file is HTTP accessibleUse a web browser or curl command to attempt an HTTP request to http://[yourdomain]/misc/cron/archive.shAffected if The file returns HTTP 200 and the script content is downloadable via HTTP without authentication
-
Inspect web server access controlsReview web server configuration (Apache .htaccess, nginx config, etc.) for the misc/ directory to see if access controls deny HTTP requestsAffected if No access restrictions are configured for the misc/ directory, or .htaccess is missing or misconfigured in misc/
-
Check file permissionsExamine file system permissions on misc/cron/archive.sh - it should not be world-readable if it contains sensitive dataAffected if The file has overly permissive read access (e.g., 644 or 664) and is located in the web root
A user is affected if misc/cron/archive.sh is present in the web document root and is directly accessible via HTTP without authentication, allowing download of the script containing sensitive credentials.
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 dataImmediately move sensitive files outside the web root directory or configure web server access controls to deny HTTP requests to misc/ and similar paths. Rotate any exposed API keys or credentials immediately.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1085 — 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-2009-1085 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