{"answers":{"affected":"4 open source packages ship an affected version, including org.eclipse.leshan:leshan-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-41034 in the wild and no public exploit code.","fix":"Upgrade org.eclipse.leshan:leshan-core to a fixed version for your release line: 1.5.0 or 2.0.0-M13.","what":"CVE-2023-41034 is a medium-severity vulnerability in eclipse-leshan leshan, published on 31 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-41034 and fix it if it is affected.\n\nWhat it is: CVE-2023-41034 is a medium-severity vulnerability in eclipse-leshan leshan, published on 31 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-41034 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.eclipse.leshan:leshan-core (Maven): affected all versions; fixed in 1.5.0\n- org.eclipse.leshan:leshan-core (Maven): affected all versions; fixed in 1.5.0\n- org.eclipse.leshan:leshan-core (Maven): affected from 2.0.0-M1; fixed in 2.0.0-M13\n- org.eclipse.leshan:leshan-core (Maven): affected from 2.0.0-M1; fixed in 2.0.0-M13\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-41034/ (Markdown: https://insights.sbomify.com/CVE-2023-41034/index.md)","id":"CVE-2023-41034","markdown":"https://insights.sbomify.com/CVE-2023-41034/index.md","name":"CVE-2023-41034","record":{"aliases":["GHSA-wc9j-gc65-3cm7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Java IoT library","requires_auth":"none","summary":"Attackers can exploit XML External Entity vulnerabilities in Eclipse Leshan by providing malicious DDF files, potentially leading to data exposure or service disruption.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"leshan","vendor":"eclipse"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"DDFFileParser in eclipse leshan is vulnerable to XXE Attacks","id":"CVE-2023-41034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xxe","year":"2023"},"n_packages":4,"n_references":5,"next":{"headline":"Macvim's Insecure Usage of IPC Mechanisms","id":"CVE-2023-41036"},"packages":[{"ecosystem":"Maven","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.leshan:leshan-core","purl":null,"source":"GHSA-wc9j-gc65-3cm7"},{"ecosystem":"Maven","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.leshan:leshan-core","purl":"pkg:maven/org.eclipse.leshan/leshan-core","source":"GHSA-wc9j-gc65-3cm7"},{"ecosystem":"Maven","fixed":["2.0.0-M13"],"introduced":["2.0.0-M1"],"last_affected":[],"package":"org.eclipse.leshan:leshan-core","purl":null,"source":"GHSA-wc9j-gc65-3cm7"},{"ecosystem":"Maven","fixed":["2.0.0-M13"],"introduced":["2.0.0-M1"],"last_affected":[],"package":"org.eclipse.leshan:leshan-core","purl":"pkg:maven/org.eclipse.leshan/leshan-core","source":"GHSA-wc9j-gc65-3cm7"}],"prev":{"headline":"Memory corruption in Parasolid V35.0","id":"CVE-2023-41033"},"products":["leshan"],"published":"2023-08-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-27","vendors":["eclipse-leshan"]},"summary":"Attackers can exploit XML External Entity vulnerabilities in Eclipse Leshan by providing malicious DDF files, potentially leading to data exposure or service disruption.","url":"https://insights.sbomify.com/CVE-2023-41034/"}