CVE-2009-5015
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 URL dispatch mechanism in TurboGears2 (aka tg2) before 2.0.2 exposes controller methods even when an @expose decoration is not used, which has unspecified impact and attack vectors.
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 · moderate confidenceTurboGears2's URL dispatch mechanism incorrectly exposes controller methods as publicly accessible URL endpoints even when the @expose decorator is not applied. This means internal methods intended to be private can be invoked via HTTP requests, potentially exposing sensitive functionality or enabling unintended actions.
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.1b2= 1.9.7a2= 1.9.7a3= 1.9.7a4= 1.9.7b1= 1.9.7b2= 2.0= 2.0.1= 2.0b1= 2.0b2= 2.0b3= 2.0b4CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 installed TurboGears2 versionRun 'pip show turbogears2' or check your project dependencies to find the exact version number of TurboGears2 installed in your environmentAffected if The installed version matches one of the affected versions: <= 2.1b2, = 1.9.7a2, = 1.9.7a3, = 1.9.7a4, = 1.9.7b1, = 1.9.7b2, = 2.0, = 2.0.1, = 2.0b1, = 2.0b2, = 2.0b3, = 2.0b4
-
Locate controller modulesFind all Python files containing controller classes in your TurboGears2 application, typically in a 'controllers' or 'model' directoryAffected if Controllers exist that contain methods without the @expose decorator
-
Inspect controller methods for @expose decoratorReview each method in your controller classes and check whether it has the @expose decorator applied; document all methods that lack this decoratorAffected if Any method in a controller class does not have the @expose decorator applied
-
Test URL accessibility of non-exposed methodsAttempt to access non-exposed controller methods via HTTP requests by constructing URLs following the pattern /controller_name/method_nameAffected if Non-exposed methods respond to HTTP requests and return valid responses instead of returning a 404 error
-
Verify method visibility in URL routingUse the TurboGears2 tool for listing routes or inspect the exposed URL mappings to see which methods are registered as accessible endpointsAffected if Methods without @expose appear in the exposed URL routes
Your environment is affected if you are running an affected TurboGears2 version AND have controller methods without the @expose decorator that are accessible via URL.
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 dataUpgrade to TurboGears2 version 2.0.2 or later which contains the fix for this URL exposure vulnerability. Alternatively, audit all controller methods to ensure only intended methods are exposed and consider adding explicit access controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-5015 — 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-5015 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