What is CVE-2014-5325?

CVE-2014-5325 is a medium-severity security vulnerability in org.directwebremoting:dwr (maven), affecting versions < 2.0.11. It is fixed in 2.0.11, 3.0.RC3.

Which versions of org.directwebremoting:dwr are affected by CVE-2014-5325?

org.directwebremoting:dwr (maven) versions < 2.0.11 is affected.

Is there a fix for CVE-2014-5325?

Yes. CVE-2014-5325 is fixed in 2.0.11, 3.0.RC3. Upgrade to this version or later.

Is CVE-2014-5325 exploitable, and should I be worried?

Whether CVE-2014-5325 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2014-5325 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2014-5325 in org.directwebremoting:dwr

Q: Which versions of org.directwebremoting:dwr are affected by CVE-2014-5325?

org.directwebremoting:dwr (maven) versions < 2.0.11 is affected.

Q: Is there a fix for CVE-2014-5325?

Yes. CVE-2014-5325 is fixed in 2.0.11, 3.0.RC3. Upgrade to this version or later.

Q: Is CVE-2014-5325 exploitable, and should I be worried?

Whether CVE-2014-5325 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2014-5325 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2014-5325?

Upgrade: org.directwebremoting:dwr to 2.0.11 or later, org.directwebremoting:dwr to 3.0.RC3 or later.

Summary

Exposure of Sensitive Information to an Unauthorized Actor in Direct Web Remoting

The (1) DOMConverter, (2) JDOMConverter, (3) DOM4JConverter, and (4) XOMConverter functions in Direct Web Remoting (DWR) through 2.0.10 and 3.x through 3.0.RC2 allow remote attackers to read arbitrary files via DOM data containing an XML external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

Impact

Affected versions

org.directwebremoting:dwr (< 2.0.11) org.directwebremoting:dwr (>= 3.0.M1, <= 3.0.RC2)

Security releases

org.directwebremoting:dwr → 2.0.11 (maven) org.directwebremoting:dwr → 3.0.RC3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.directwebremoting:dwr to 2.0.11 or later; org.directwebremoting:dwr to 3.0.RC3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2014-5325? CVE-2014-5325 is a medium-severity security vulnerability in org.directwebremoting:dwr (maven), affecting versions < 2.0.11. It is fixed in 2.0.11, 3.0.RC3.
Which versions of org.directwebremoting:dwr are affected by CVE-2014-5325? org.directwebremoting:dwr (maven) versions < 2.0.11 is affected.
Is there a fix for CVE-2014-5325? Yes. CVE-2014-5325 is fixed in 2.0.11, 3.0.RC3. Upgrade to this version or later.
Is CVE-2014-5325 exploitable, and should I be worried? Whether CVE-2014-5325 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2014-5325 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2014-5325?
- Upgrade org.directwebremoting:dwr to 2.0.11 or later
- Upgrade org.directwebremoting:dwr to 3.0.RC3 or later

Other vulnerabilities in org.directwebremoting:dwr

CVE-IDSeverityPackage summary

CVE-2014-5326Mediumorg.directwebremoting:dwr: Improper Neutralization of Input During Web Page Generation in Direct Web Remoting CVE-2007-0185Highorg.directwebremoting:dwr: Direct Web Remoting vulnerable to Denial of Service CVE-2007-0184Highorg.directwebremoting:dwr: Incorrect Authorization in Getahead Direct Web Remoting