What is CVE-2020-17531?

CVE-2020-17531 is a critical-severity insecure deserialization vulnerability in org.apache.tapestry:tapestry-project (maven), affecting versions >= 4.0, < 5.0.1. It is fixed in 5.0.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is CVE-2020-17531?

CVE-2020-17531 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.tapestry:tapestry-project are affected by CVE-2020-17531?

org.apache.tapestry:tapestry-project (maven) versions >= 4.0, < 5.0.1 is affected.

Is there a fix for CVE-2020-17531?

Yes. CVE-2020-17531 is fixed in 5.0.1. Upgrade to this version or later.

Is CVE-2020-17531 exploitable, and should I be worried?

Whether CVE-2020-17531 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-2020-17531 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-2020-17531

Q: How severe is CVE-2020-17531?

CVE-2020-17531 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.apache.tapestry:tapestry-project are affected by CVE-2020-17531?

org.apache.tapestry:tapestry-project (maven) versions >= 4.0, < 5.0.1 is affected.

Q: Is there a fix for CVE-2020-17531?

Yes. CVE-2020-17531 is fixed in 5.0.1. Upgrade to this version or later.

Q: Is CVE-2020-17531 exploitable, and should I be worried?

Whether CVE-2020-17531 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-2020-17531 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-2020-17531?

Upgrade org.apache.tapestry:tapestry-project to 5.0.1 or later.

Summary

Serialization vulnerability in Apache Tapestry

A Java Serialization vulnerability was found in Apache Tapestry 4. Apache Tapestry 4 will attempt to deserialize the "sp" parameter even before invoking the page's validate method, leading to deserialization without authentication. Apache Tapestry 4 reached end of life in 2008 and no update to address this issue will be released. Apache Tapestry 5 versions are not vulnerable to this issue. Users of Apache Tapestry 4 should upgrade to the latest Apache Tapestry 5 version.

Impact

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2020-17531 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.0.1); upgrading removes the vulnerable code path.

Affected versions

org.apache.tapestry:tapestry-project (>= 4.0, < 5.0.1)

Security releases

org.apache.tapestry:tapestry-project → 5.0.1 (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 org.apache.tapestry:tapestry-project to 5.0.1 or later to resolve this vulnerability.

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

Frequently Asked Questions

What is CVE-2020-17531? CVE-2020-17531 is a critical-severity insecure deserialization vulnerability in org.apache.tapestry:tapestry-project (maven), affecting versions >= 4.0, < 5.0.1. It is fixed in 5.0.1. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is CVE-2020-17531? CVE-2020-17531 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.tapestry:tapestry-project are affected by CVE-2020-17531? org.apache.tapestry:tapestry-project (maven) versions >= 4.0, < 5.0.1 is affected.
Is there a fix for CVE-2020-17531? Yes. CVE-2020-17531 is fixed in 5.0.1. Upgrade to this version or later.
Is CVE-2020-17531 exploitable, and should I be worried? Whether CVE-2020-17531 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-2020-17531 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-2020-17531? Upgrade org.apache.tapestry:tapestry-project to 5.0.1 or later.