Skip to content

← Public intelligence

Maven package

org.eclipse.leshan:leshan-core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5MavenPublished

    DDFFileParser is vulnerable to XXE Attacks

    CVE-2023-41034 · GHSA-wc9j-gc65-3cm7

    Affected
    • Maven org.eclipse.leshan:leshan-core < 1.5.0; >= 2.0.0-M1, < 2.0.0-M13
    Fixed in
    1.5.02.0.0-M13· Vendor fix available
    Issue
    Impact DDFFileParser and DefaultDDFFileValidator (and so ObjectLoader) are vulnerable to XXE AttacksProcessing). 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. 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 : References - https://owasp.org/www-community/vulnerabilities/XMLExternalEntity(XXE)Processing - https://cheatsheetseries.owasp.org/cheatsheets/XMLExternalEntityPreventionCheatSheet.html - https://semgrep.dev/docs/cheat-sheets/java-xxe/ - https://community.veracode.com/s/article/Java-Remediation-Guidance-for-XXE

    Recommended action: Upgrade to 2.0.0-M13 (pre-release) or 1.5.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →