CVE-2007-2377
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 Getahead Direct Web Remoting (DWR) framework 1.1.4 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 · moderate confidenceDirect Web Remoting (DWR) 1.1.4 returns JSON data without any protection mechanism (such as CSRF tokens, origin validation, or JSONP callback functions), allowing attackers to retrieve sensitive data by embedding DWR endpoints in the SRC attribute of SCRIPT tags on malicious pages and exfiltrating the response data via JavaScript.
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.1.4CVSS 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 if DWR is installedSearch for dwr.jar in the application's WEB-INF/lib directory, or look for /dwr/ or /dwr/index.html endpoint paths in the deployed web applicationAffected if DWR library files or DWR-related URL paths are present in the application
-
Determine DWR versionInspect the dwr.jar file metadata (MANIFEST.MF) or check version info in DWR's /dwr/index.html page that lists available beans/exposed methodsAffected if The installed DWR version is exactly 1.1.4
-
Locate DWR JSON endpointsAccess /dwr/ or check the DWT configuration for exposed Java bean methods. Typical endpoint URLs follow pattern: /dwr/call/plaincall/<class>.<method>.dwrAffected if DWR endpoints are accessible and return JSON responses
-
Verify authentication requirementAttempt to access DWR endpoints without providing credentials or session cookies. Check if HTTP 401/403 is returned or if login is requiredAffected if DWR endpoints return data without requiring authentication
-
Check for CSRF protectionInspect DWR configuration files (web.xml, dwr.xml) for CSRF token enforcement settings, or examine HTTP responses for token requirements when making requestsAffected if No CSRF tokens or origin validation is enforced on DWR JSON responses
The environment is affected if DWR version 1.1.4 is installed and its JSON endpoints are accessible without authentication or CSRF protection mechanisms.
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 CSRF protection tokens, validate HTTP Referer/Origin headers, or require authentication for all DWR JSON endpoints to prevent unauthorized cross-origin data access.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2377 — 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-2377 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