CVE-2023-41034 json
DDFFileParser in eclipse leshan is vulnerable to XXE Attacks
published 3y ago modified 2mo ago also GHSA-wc9j-gc65-3cm7 , EUVD-2023-2373
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
Eclipse Leshan is a device management server and client Java implementation. In affected versions DDFFileParser` and `DefaultDDFFileValidator` (and so `ObjectLoader`) are vulnerable to `XXE Attacks`. A DDF file is a LWM2M format used to store LWM2M object description. Leshan users are impacted only if they parse untrusted DDF files (e.g. if they let external users provide their own model), in that case they MUST upgrade to fixed version. If you parse only trusted DDF file and validate only with trusted xml schema, upgrading is not mandatory. This issue has been fixed in versions 1.5.0 and 2.0.0-M13. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Patch / fix
- maven org.eclipse.leshan:leshan-core 1.5.0, 2.0.0-M13
- eclipse leshan 1.5.0
Is CVE-2023-41034 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-15).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.eclipse.leshan:leshan-core | <1.5.0 >=2.0.0-M1, <2.0.0-M13 |
1.5.0 2.0.0-M13 |
Affected products
- eclipse-leshan leshan
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
github.com
/eclipse-leshan/leshan/commit/29577d2879ba8e7674c3b216a7f01193fc7ae013
web, patch
-
github.com
/eclipse-leshan/leshan/commit/4d3e63ac271a817f81fba3e3229c519af7a3049c
web, patch
-
github.com
/eclipse-leshan/leshan/security/advisories/GHSA-wc9j-gc65-3cm7
web, mitigation, third-party-advisory
-
github.com
/eclipse-leshan/leshan/wiki/Adding-new-objects#the-lwm2m-model
web, product
-
owasp.org
/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing
web, not-applicable
-
nvd.nist.gov
/vuln/detail/CVE-2023-41034
advisory
-
github.com
/eclipse-leshan/leshan
package
Sources
- CVE List CVE-2023-41034
- GitHub Advisory GHSA-wc9j-gc65-3cm7
- NVD CVE-2023-41034
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.