First published: Thu Aug 31 2023(Updated: )
### Impact `DDFFileParser` and `DefaultDDFFileValidator` (and so `ObjectLoader`) are vulnerable to [XXE Attacks](https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing). [DDF file](https://github.com/eclipse-leshan/leshan/wiki/Adding-new-objects#the-lwm2m-model) 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. ### Patches This is fixed in **v1.5.0** and **2.0.0-M13**. ### Workarounds No easy way. Eventually writing your own `DDFFileParser`/`DefaultDDFFileValidator` (and so `ObjectLoader`) creating a `DocumentBuilderFactory` with : ```java // For DDFFileParser DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true); factory.setFeature("http://apache.org/xml/features/disallow-doctype-decl", true); // Disable DTDs factory.setXIncludeAware(false); // Disable XML Inclusions factory.setExpandEntityReferences(false); // disable expand entity reference nodes // For DefaultDDFFileValidator SchemaFactory factory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI); factory.setFeature(XMLConstants.FEATURE_SECURE_PROCESSING, true); factory.setProperty(XMLConstants.ACCESS_EXTERNAL_DTD, ""); factory.setProperty(XMLConstants.ACCESS_EXTERNAL_SCHEMA, ""); ``` ### References - https://owasp.org/www-community/vulnerabilities/XML_External_Entity_(XXE)_Processing - https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html - https://semgrep.dev/docs/cheat-sheets/java-xxe/ - https://community.veracode.com/s/article/Java-Remediation-Guidance-for-XXE
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.eclipse.leshan:leshan-core | >=2.0.0-M1<2.0.0-M13 | 2.0.0-M13 |
maven/org.eclipse.leshan:leshan-core | <1.5.0 | 1.5.0 |
Eclipse Leshan | <1.5.0 | |
Eclipse Leshan | =2.0.0-milestone1 | |
Eclipse Leshan | =2.0.0-milestone10 | |
Eclipse Leshan | =2.0.0-milestone11 | |
Eclipse Leshan | =2.0.0-milestone12 | |
Eclipse Leshan | =2.0.0-milestone2 | |
Eclipse Leshan | =2.0.0-milestone3 | |
Eclipse Leshan | =2.0.0-milestone4 | |
Eclipse Leshan | =2.0.0-milestone5 | |
Eclipse Leshan | =2.0.0-milestone6 | |
Eclipse Leshan | =2.0.0-milestone7 | |
Eclipse Leshan | =2.0.0-milestone8 | |
Eclipse Leshan | =2.0.0-milestone9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-41034 is a vulnerability in Eclipse Leshan, a device management server and client Java implementation.
CVE-2023-41034 allows for XXE (XML External Entity) attacks which can lead to unauthorized data disclosure and server-side request forgery.
Yes, upgrading to version 2.0.0-M13 or higher for Leshan Core resolves the vulnerability.
CVE-2023-41034 has a severity rating of 9.8 (Critical).
You can find more information about CVE-2023-41034 on the Eclipse Leshan GitHub repository and the associated security advisories.