What is CVE-2013-1768?

CVE-2013-1768 is a high-severity insecure deserialization vulnerability in org.apache.openjpa:openjpa (maven), affecting versions >= 1.0.0, < 1.2.3. It is fixed in 1.2.3, 2.2.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

Which versions of org.apache.openjpa:openjpa are affected by CVE-2013-1768?

org.apache.openjpa:openjpa (maven) versions >= 1.0.0, < 1.2.3 is affected.

Is there a fix for CVE-2013-1768?

Yes. CVE-2013-1768 is fixed in 1.2.3, 2.2.2. Upgrade to this version or later.

Is CVE-2013-1768 exploitable, and should I be worried?

Whether CVE-2013-1768 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-2013-1768 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-2013-1768 in org.apache.openjpa:openjpa

Q: Which versions of org.apache.openjpa:openjpa are affected by CVE-2013-1768?

org.apache.openjpa:openjpa (maven) versions >= 1.0.0, < 1.2.3 is affected.

Q: Is there a fix for CVE-2013-1768?

Yes. CVE-2013-1768 is fixed in 1.2.3, 2.2.2. Upgrade to this version or later.

Q: Is CVE-2013-1768 exploitable, and should I be worried?

Whether CVE-2013-1768 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-2013-1768 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-2013-1768?

Upgrade: org.apache.openjpa:openjpa to 1.2.3 or later, org.apache.openjpa:openjpa to 2.2.2 or later.

Summary

Deserialization of Untrusted Data in Apache OpenJPA

The BrokerFactory functionality in Apache OpenJPA 1.x before 1.2.3 and 2.x before 2.2.2 creates local executable JSP files containing logging trace data produced during deserialization of certain crafted OpenJPA objects, which makes it easier for remote attackers to execute arbitrary code by creating a serialized object and leveraging improperly secured server programs.

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.

Affected versions

org.apache.openjpa:openjpa (>= 1.0.0, < 1.2.3) org.apache.openjpa:openjpa (>= 2.0.0, < 2.2.2)

Security releases

org.apache.openjpa:openjpa → 1.2.3 (maven) org.apache.openjpa:openjpa → 2.2.2 (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.apache.openjpa:openjpa to 1.2.3 or later; org.apache.openjpa:openjpa to 2.2.2 or later

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

Frequently Asked Questions

What is CVE-2013-1768? CVE-2013-1768 is a high-severity insecure deserialization vulnerability in org.apache.openjpa:openjpa (maven), affecting versions >= 1.0.0, < 1.2.3. It is fixed in 1.2.3, 2.2.2. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
Which versions of org.apache.openjpa:openjpa are affected by CVE-2013-1768? org.apache.openjpa:openjpa (maven) versions >= 1.0.0, < 1.2.3 is affected.
Is there a fix for CVE-2013-1768? Yes. CVE-2013-1768 is fixed in 1.2.3, 2.2.2. Upgrade to this version or later.
Is CVE-2013-1768 exploitable, and should I be worried? Whether CVE-2013-1768 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-2013-1768 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-2013-1768?
- Upgrade org.apache.openjpa:openjpa to 1.2.3 or later
- Upgrade org.apache.openjpa:openjpa to 2.2.2 or later