CVE-2008-2318
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 WOHyperlink implementation in WebObjects in Apple Xcode tools before 3.1 appends local session IDs to generated non-local URLs, which allows remote attackers to obtain potentially sensitive information by reading the requests for these URLs.
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 confidenceThe WOHyperlink component in WebObjects (part of Apple Xcode tools before 3.1) incorrectly appends local session identifiers to generated URLs intended for external/non-local destinations. When users click these links, their session IDs are transmitted in the URL query parameters to external sites, potentially exposing session credentials to third parties who can read the HTTP requests.
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.5= 2.2<= 3.0= 1.0= 2.0= 2.1= 2.2.1= 2.3= 2.4= 2.4.1= 2.5CVSS 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 WebObjects/WOHyperlink usageSearch your project source code for imports or references to WebObjects.framework, WOFramework, or usage of WOHyperlink component tags in .wo filesAffected if Your application uses WebObjects with the WOHyperlink component for generating hyperlinks
-
Check installed Xcode versionRun 'xcodebuild -version' in terminal to get the Xcode version, or check /Applications/Xcode.app/Contents/version.plistAffected if Xcode version matches 1.5, 2.2, or any version up to and including 3.0 from the affected list
-
Check WebObjects framework versionLocate WebObjects.framework in your Xcode tools directory (typically in /System/Library/Frameworks or within Xcode.app/Contents/Developer) and query its version infoAffected if The WebObjects framework version corresponds to an affected Xcode tools version (1.0 through 3.0)
-
Inspect generated hyperlink URLs for session leakageEnable URL logging in your WebObjects application or capture HTTP traffic when clicking WOHyperlink-generated links pointing to external domains; examine query parameters for session identifiers (jsessionid, woInstance, or similar)Affected if URLs destined for external/non-local domains contain session ID parameters in the query string
You are affected if your environment runs Xcode/WebObjects versions 1.0-3.0 and uses WOHyperlink to generate links that direct to external URLs, with session IDs visible in the URL query parameters.
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 Xcode 3.1 or later which contains the fixed WebObjects implementation. For applications using custom WOHyperlink configurations, audit all hyperlink generation to ensure session IDs are not appended to non-local URLs.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-2318 — 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-2008-2318 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