NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2023-4043 — project

MEDIUMFix: eclipse-ee4j/parsson#100

CVE-2023-4043 is a medium-severity (CVSS 5.9) Improper Input Validation vulnerability in org.eclipse.parsson:project. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.eclipse.parsson:project — see the affected versions and patch details below.

Parsson DoS when parsing numbers from untrusted sources

Also known asGHSA-g8p6-p27c-52fx
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-4043.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk+0.13%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.46%0.93%1.39%0.1%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.eclipse.parsson:project☕org.eclipse.parsson:project

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.eclipse.parsson:project≥ 1.1.0&&< 1.1.41.1.4org.eclipse.parsson:project:1.1.4
☕Mavenorg.eclipse.parsson:projectall versions1.0.5org.eclipse.parsson:project:1.0.5

Affected Products

1 product · 2 configurations
Application
parssoneclipse
≥ 1.1.0 && < 1.1.4
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Eclipse Parsson before versions 1.1.4 and 1.0.5, Parsing JSON from un…

gitlab.eclipse.orgNVDNov 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.parsson:project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.eclipse.parsson:project to 1.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-4043 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat rates this as an important impact since one needs to process untrusted and if there is no sanitization a Denial of Service (DoS) may happen.

Workaround published by Red Hat
Avoid processing untrusted sources content in order to minimize the chance for Denial of Service attack.
Source: Red Hat security advisory for CVE-2023-4043 (CC BY 4.0)
ProductFixed inAdvisory
Cryostat 2 on RHEL 8cryostat-tech-preview/cryostat-grafana-dashboard-rhel8:2.4.0-4RHSA-2024:0530
EAP 8.0.1parssonRHSA-2024:1194
Red Hat build of Quarkus 3.2.10.Finalorg.eclipse.parsson/parsson:1.1.5.redhat-00001RHSA-2024:0722
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8eap8-apache-sshd-0:2.12.0-1.redhat_00001.1.el8eapRHSA-2024:1192
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9eap8-apache-sshd-0:2.12.0-1.redhat_00001.1.el9eapRHSA-2024:1193
RHBOAC camel-quarkus 3 (camel-4.0/quarkus-3.2)parssonRHSA-2024:0789
RHINT Camel-Springboot 4.0.3parssonRHSA-2024:0793

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2023-4043 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-4043: project — Fixed in 1.1.4