What is CVE-2023-4043?

CVE-2023-4043 is a medium-severity improper input validation vulnerability in org.eclipse.parsson:project (maven), affecting versions >= 1.1.0, < 1.1.4. It is fixed in 1.1.4, 1.0.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2023-4043?

CVE-2023-4043 has a CVSS score of 5.9 (Medium). 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.eclipse.parsson:project are affected by CVE-2023-4043?

org.eclipse.parsson:project (maven) versions >= 1.1.0, < 1.1.4 is affected.

Is there a fix for CVE-2023-4043?

Yes. CVE-2023-4043 is fixed in 1.1.4, 1.0.5. Upgrade to this version or later.

Is CVE-2023-4043 exploitable, and should I be worried?

Whether CVE-2023-4043 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-2023-4043 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-2023-4043 in org.eclipse.parsson:project

Q: How severe is CVE-2023-4043?

CVE-2023-4043 has a CVSS score of 5.9 (Medium). 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.eclipse.parsson:project are affected by CVE-2023-4043?

org.eclipse.parsson:project (maven) versions >= 1.1.0, < 1.1.4 is affected.

Q: Is there a fix for CVE-2023-4043?

Yes. CVE-2023-4043 is fixed in 1.1.4, 1.0.5. Upgrade to this version or later.

Q: Is CVE-2023-4043 exploitable, and should I be worried?

Whether CVE-2023-4043 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-2023-4043 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-2023-4043?

Upgrade: org.eclipse.parsson:project to 1.1.4 or later, org.eclipse.parsson:project to 1.0.5 or later.

Summary

Eclipse Parsson Denial of Service vulnerability

In Eclipse Parsson before versions 1.1.4 and 1.0.5, Parsing JSON from untrusted sources can lead malicious actors to exploit the fact that the built-in support for parsing numbers with large scale in Java has a number of edge cases where the input text of a number can lead to much larger processing time than one would expect.

To mitigate the risk, parsson put in place a size limit for the numbers as well as their scale.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2023-4043 has a CVSS score of 5.9 (Medium). 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 (1.1.4, 1.0.5); upgrading removes the vulnerable code path.

Affected versions

org.eclipse.parsson:project (>= 1.1.0, < 1.1.4) org.eclipse.parsson:project (< 1.0.5)

Security releases

org.eclipse.parsson:project → 1.1.4 (maven) org.eclipse.parsson:project → 1.0.5 (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.eclipse.parsson:project to 1.1.4 or later; org.eclipse.parsson:project to 1.0.5 or later

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

Frequently Asked Questions

What is CVE-2023-4043? CVE-2023-4043 is a medium-severity improper input validation vulnerability in org.eclipse.parsson:project (maven), affecting versions >= 1.1.0, < 1.1.4. It is fixed in 1.1.4, 1.0.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2023-4043? CVE-2023-4043 has a CVSS score of 5.9 (Medium). 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.eclipse.parsson:project are affected by CVE-2023-4043? org.eclipse.parsson:project (maven) versions >= 1.1.0, < 1.1.4 is affected.
Is there a fix for CVE-2023-4043? Yes. CVE-2023-4043 is fixed in 1.1.4, 1.0.5. Upgrade to this version or later.
Is CVE-2023-4043 exploitable, and should I be worried? Whether CVE-2023-4043 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-2023-4043 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-2023-4043?
- Upgrade org.eclipse.parsson:project to 1.1.4 or later
- Upgrade org.eclipse.parsson:project to 1.0.5 or later