CVE-2007-2385
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 Yahoo! UI framework exchanges data using JavaScript Object Notation (JSON) without an associated protection scheme, which allows remote attackers to obtain the data via a web page that retrieves the data through a URL in the SRC attribute of a SCRIPT element and captures the data using other JavaScript code, aka "JavaScript Hijacking."
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 confidenceThe Yahoo! UI framework returns JSON data without proper protection mechanisms (missing Content-Type headers, no anti-CSRF tokens, no callback wrappers). Attackers can exploit this by embedding a SCRIPT tag pointing to the JSON endpoint on a malicious page, allowing the browser to execute the returned JSON as JavaScript and exfiltrate the data to attacker-controlled servers.
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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 Yahoo UI Library in useSearch your codebase, dependencies, or deployed files for 'yui', 'yahoo ui', or the specific Yahoo UI Library JavaScript files (such as yahoo.js, json.js, or connection.js)Affected if The Yahoo UI Library is found in your environment - all versions are affected by this vulnerability
-
Inventory JSON-producing endpointsReview your application for endpoints that return JSON data, particularly those that utilize the Yahoo UI Library's JSON handling or connection utilitiesAffected if JSON endpoints exist that were built with or depend on the Yahoo UI Library's JSON functionality
-
Inspect JSON response headersMake a request to your JSON endpoints and examine the HTTP response headers, specifically looking for the Content-Type header valueAffected if The Content-Type header is missing, set to text/plain, or set to a non-application/json value - this allows browsers to execute the response as JavaScript
-
Verify cross-origin JSON accessibilityTest whether your JSON endpoints can be accessed via a SCRIPT tag from a different origin (or check if the Same-Origin Policy is enforced and if JSONP callbacks are enabled)Affected if JSON data can be loaded via SCRIPT tag from a different origin, or JSONP callbacks (wrappers) are present without proper origin validation
If your environment uses the Yahoo UI Library and exposes JSON endpoints that lack proper Content-Type: application/json headers and can be accessed cross-origin via SCRIPT tags, you are affected by this vulnerability.
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 dataImplement proper Content-Type: application/json headers, use JSON with callback wrappers (JSONP), add anti-CSRF tokens for state-changing operations, and ensure sensitive JSON endpoints require authentication and same-origin constraints.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2385 — 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-2007-2385 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