CVE-2007-0184
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 · uneditedGetahead Direct Web Remoting (DWR) before 1.1.4 allows attackers to obtain unauthorized access to public methods via a crafted request that bypasses the include/exclude checks.
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 confidenceGetahead Direct Web Remoting (DWR) before version 1.1.4 contains an access control bypass vulnerability. Attackers can craft malicious requests that bypass the include/exclude security checks, allowing unauthorized access to public methods that should be restricted.
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.3= 0.7= 0.8= 0.9= 1.0= 1.1.0= 1.1.1= 1.1.2CVSS 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.
-
Locate the DWR JAR fileSearch for dwr*.jar in your application's WEB-INF/lib directory or classpath. The JAR filename typically includes the version number (for example, dwr-1.1.3.jar).Affected if The JAR file version is 1.1.3 or earlier, or matches 0.7, 0.8, 0.9, 1.0, 1.1.0, 1.1.1, or 1.1.2.
-
Verify the exact DWR versionOpen the JAR file and inspect the META-INF/MANIFEST.MF file for the Implementation-Version or Bundle-Version attribute.Affected if The version listed is 1.1.3 or any of the other affected versions listed in the CVE.
-
Locate the DWR configuration fileSearch for dwr.xml files in your application. These are typically found in WEB-INF/ or on the classpath. Also check for web.xml entries that reference DWR servlets.Affected if A dwr.xml configuration file exists in the application.
-
Identify if include/exclude security is configuredExamine the dwr.xml file for <allow> or <exclude> tags that define method-level access restrictions. These tags control which Java methods are exposed and which are restricted.Affected if The dwr.xml contains include/exclude rules that restrict access to certain methods, because the vulnerability allows these restrictions to be bypassed.
-
Check for exposed sensitive methodsReview all Java classes configured in dwr.xml that are exposed via DWR. Look for methods that perform sensitive operations (database access, authentication, authorization, file operations).Affected if Sensitive or restricted methods are exposed through DWR with include/exclude rules, and the DWR version is vulnerable.
Your environment is affected if DWR version 1.1.3 or earlier is deployed AND you have include/exclude security rules configured in dwr.xml for restricting access to certain methods.
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 DWR to version 1.1.4 or later to obtain the security fix that properly enforces include/exclude access controls on all method calls.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0184 — 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-0184 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