{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.juddi:juddi-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-37578 in the wild and no public exploit code.","fix":"Upgrade org.apache.juddi:juddi-core to 3.3.10 or later.","what":"CVE-2021-37578 is a critical unsafe deserialization vulnerability in Apache jUDDI, published on 29 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-37578 and fix it if it is affected.\n\nWhat it is: CVE-2021-37578 is a critical unsafe deserialization vulnerability in Apache jUDDI, published on 29 Jul 2021. 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-2021-37578 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.juddi:juddi-core (Maven): affected all versions; fixed in 3.3.10\n- org.apache.juddi:juddi-core (Maven): affected all versions; fixed in 3.3.10\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-2021-37578/ (Markdown: https://insights.sbomify.com/CVE-2021-37578/index.md)","id":"CVE-2021-37578","markdown":"https://insights.sbomify.com/CVE-2021-37578/index.md","name":"CVE-2021-37578","record":{"aliases":["GHSA-9hx8-2mrv-r674"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Java UDDI library","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via malicious serialized objects in Apache jUDDI if the optional RMI feature is enabled.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"juddi","vendor":"apache"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Apache jUDDI uses several classes related to Java's Remote Method Invocation (RMI) which (as an extension to UDDI) provides an alternate transport for accessing UDDI services. RMI uses the default Java serialization mechanism to pass parameters in RMI invocations. A remote attacker can send a malicious serialized object to the above RMI entries. The objects get deserialized without any check on the incoming data. In the worst case, it may let the attacker run arbitrary code remotely. For both jUDDI web service applications and jUDDI clients, the usage of RMI is disabled by default. Since this is an optional feature and an extension to the UDDI protocol, the likelihood of impact is low. Starting with 3.3.10, all RMI related code was removed.","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":"Remote code execution via RMI","id":"CVE-2021-37578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2021"},"n_packages":2,"n_references":2,"next":{"headline":"Bypass deserialization checks in Apache Dubbo","id":"CVE-2021-37579"},"packages":[{"ecosystem":"Maven","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"org.apache.juddi:juddi-core","purl":null,"source":"GHSA-9hx8-2mrv-r674"},{"ecosystem":"Maven","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"org.apache.juddi:juddi-core","purl":"pkg:maven/org.apache.juddi/juddi-core","source":"GHSA-9hx8-2mrv-r674"}],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2021-37577"},"products":["Apache jUDDI"],"published":"2021-07-29","related":[{"cvss_score":8.1,"headline":"Apache juddi-client vulnerable to XML External Entity (XXE)","id":"CVE-2018-1307","kev_date_added":null,"published":"2018-02-09"},{"cvss_score":6.5,"headline":"Other in jUDDI","id":"CVE-2009-4267","kev_date_added":null,"published":"2018-02-19"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2009-1198","kev_date_added":null,"published":"2017-10-30"},{"cvss_score":6.1,"headline":"Moderate severity vulnerability that affects org.apache.juddi:juddi-client","id":"CVE-2015-5241","kev_date_added":null,"published":"2017-05-19"},{"cvss_score":5.3,"headline":"Other in n/a","id":"CVE-2009-1197","kev_date_added":null,"published":"2017-10-30"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Apache Software Foundation"]},"summary":"Remote attackers can execute arbitrary code via malicious serialized objects in Apache jUDDI if the optional RMI feature is enabled.","url":"https://insights.sbomify.com/CVE-2021-37578/"}