{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.iotdb:iotdb-parent. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1952 in the wild and no public exploit code.","fix":"Upgrade org.apache.iotdb:iotdb-parent to 0.9.2 or later.","what":"CVE-2020-1952 is a critical missing authorization vulnerability in Apache IoTDB, published on 27 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-1952 and fix it if it is affected.\n\nWhat it is: CVE-2020-1952 is a critical missing authorization vulnerability in Apache IoTDB, published on 27 Apr 2020. 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-2020-1952 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.iotdb:iotdb-parent (Maven): affected all versions; fixed in 0.9.2\n- org.apache.iotdb:iotdb-parent (Maven): affected all versions; fixed in 0.9.2\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-2020-1952/ (Markdown: https://insights.sbomify.com/CVE-2020-1952/index.md)","id":"CVE-2020-1952","markdown":"https://insights.sbomify.com/CVE-2020-1952/index.md","name":"CVE-2020-1952","record":{"aliases":["GHSA-wc6f-cjcp-cc33"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache IoTDB","requires_auth":"none","summary":"Attackers can execute arbitrary code remotely via the exposed JMX port due to lack of authentication in Apache IoTDB.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"iotdb","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-295","name":"Improper Certificate Validation"}],"description":"An issue was found in Apache IoTDB .9.0 to 0.9.1 and 0.8.0 to 0.8.2. When starting IoTDB, the JMX port 31999 is exposed with no certification.Then, clients could execute code remotely.","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":"Improper Certificate Validation in Apache IoTDB","id":"CVE-2020-1952","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2020"},"n_packages":2,"n_references":1,"next":{"headline":"Remote code execution in Apache Commons Configuration","id":"CVE-2020-1953"},"packages":[{"ecosystem":"Maven","fixed":["0.9.2"],"introduced":["0"],"last_affected":[],"package":"org.apache.iotdb:iotdb-parent","purl":null,"source":"GHSA-wc6f-cjcp-cc33"},{"ecosystem":"Maven","fixed":["0.9.2"],"introduced":["0"],"last_affected":[],"package":"org.apache.iotdb:iotdb-parent","purl":"pkg:maven/org.apache.iotdb/iotdb-parent","source":"GHSA-wc6f-cjcp-cc33"}],"prev":{"headline":"Infinite Loop in Apache Tika","id":"CVE-2020-1951"},"products":["IoTDB"],"published":"2020-04-27","related":[{"cvss_score":9.8,"headline":"Apache IoTDB: Path Traversal in DataNode Internal RPC Trigger JAR Upload Allows Arbitrary File Write","id":"CVE-2026-24014","kev_date_added":null,"published":"2026-07-06"},{"cvss_score":9.8,"headline":"Apache IoTDB: Insecure Default Configuration Vulnerability","id":"CVE-2026-24015","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.8,"headline":"Apache IoTDB: JEXL Expression Injection Vulnerability","id":"CVE-2026-24713","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.8,"headline":"Apache IoTDB: Remote Code Execution with untrusted URI of User-defined function","id":"CVE-2024-24780","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":9.8,"headline":"Apache IoTDB: Remote Code Execution (RCE) risk via the UDF","id":"CVE-2023-46226","kev_date_added":null,"published":"2024-01-15"},{"cvss_score":9.8,"headline":"Apache IoTDB: Unsafe deserialize map in Sync Tool","id":"CVE-2023-51656","kev_date_added":null,"published":"2023-12-21"},{"cvss_score":9.8,"headline":"Apache IoTDB grafana-connector Login Bypass Vulnerability","id":"CVE-2023-24831","kev_date_added":null,"published":"2023-04-17"}],"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"]},"summary":"Attackers can execute arbitrary code remotely via the exposed JMX port due to lack of authentication in Apache IoTDB.","url":"https://insights.sbomify.com/CVE-2020-1952/"}