CVE-2009-1052
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 · uneditedFireAnt 1.3 and earlier stores sensitive information under the web root with insufficient access control, which allows remote attackers to download a database containing user credentials via a direct request for user.tsv.
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 confidenceFireAnt 1.3 and earlier stores the user.tsv database file containing user credentials in a web-accessible directory without proper access controls, allowing any remote attacker to directly download the file by requesting user.tsv.
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.3= 1.0= 1.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
- 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 FireAnt installationCheck if the FireAnt application files exist on the server, typically in the web root or application directory. Look for files such as index.php, fireant.php, or a 'fireant' subdirectory.Affected if FireAnt application files are present on the server
-
Determine FireAnt versionExamine the version information in the application source files, such as a version.php file, or check the main PHP file for a version declaration. Compare against affected versions: 1.0, 1.2, and 1.3 or earlier.Affected if Installed version is 1.3 or earlier (1.0, 1.2, or 1.3)
-
Locate the user.tsv fileSearch for the user.tsv file within the web application directory structure. Common paths include the application root or a data/storage subdirectory.Affected if user.tsv file exists in the application directory
-
Verify user.tsv is web-accessibleCheck if the directory containing user.tsv is within the web server's document root (web root). Examine the web server configuration to confirm whether this directory is served publicly.Affected if user.tsv is stored inside the web server document root
-
Test direct HTTP access to user.tsvAttempt to request the user.tsv file via HTTP from an external host or use a web browser to navigate to the direct URL (for example: http://target/fireant/user.tsv). A successful download indicates the vulnerability is present.Affected if The user.tsv file can be downloaded directly via HTTP without authentication
A server is affected if FireAnt version 1.3 or earlier is installed and the user.tsv file is accessible via direct HTTP request from within the web root.
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 user.tsv database file outside the web root directory, or configure web server access controls (e.g., deny direct access) to prevent unauthorized downloads.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1052 — 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-1052 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