CVE-2009-1223
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 · uneditedaspWebCalendar Free Edition 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 calendar/calendar.mdb.
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 confidenceaspWebCalendar Free Edition stores its Microsoft Access database (calendar.mdb) containing user credentials in a web-accessible directory. The lack of access control allows any remote attacker to directly download the database file via HTTP request to calendar/calendar.mdb, exposing all stored user 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 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
- 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.
-
Confirm aspWebCalendar is installedLocate aspWebCalendar installation files or the application web directory on the server. Look for typical paths like /calendar/ or /aspwebcalendar/ under the web root.Affected if aspWebCalendar Free Edition is present on the server
-
Check for calendar.mdb in web directorySearch for the file calendar.mdb within the web-accessible portion of the application directory. Common locations include calendar/calendar.mdb or aspwebcalendar/calendar/calendar.mdb.Affected if The file calendar.mdb exists in any subdirectory under the web root
-
Test direct HTTP access to database fileUsing a browser or curl/wget, attempt to retrieve the database file via HTTP: http://[target]/calendar/calendar.mdb or similar path. Check if the file downloads without authentication.Affected if The calendar.mdb file downloads without requiring any authentication or login
-
Verify database contains user credentialsIf the file downloads, open calendar.mdb with Microsoft Access or a compatible tool. Look for tables containing usernames and passwords.Affected if The database file is accessible and contains user credential data
The environment is affected if aspWebCalendar is installed and the calendar.mdb database file is accessible via direct HTTP request without authentication.
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 dataRelocate the database file outside the web root directory and update the application's connection path, or implement proper authentication/authorization controls to prevent unauthenticated access to the database file.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1223 — 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-1223 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