{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-12852 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-12852 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-12852 is a medium-severity code injection vulnerability in n/a, published on 4 Jun 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-12852 and fix it if it is affected.\n\nWhat it is: CVE-2020-12852 is a medium-severity code injection vulnerability in n/a, published on 4 Jun 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-12852 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-12852/ (Markdown: https://insights.sbomify.com/CVE-2020-12852/index.md)","id":"CVE-2020-12852","markdown":"https://insights.sbomify.com/CVE-2020-12852/index.md","name":"CVE-2020-12852","record":{"aliases":["GHSA-jp5w-2f3c-7r7m"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Pydio Cells","requires_auth":"high_privilege","summary":"Administrators can exploit the update feature to replace the application binary with a malicious one, leading to remote code execution upon service restart.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cells","vendor":"pydio"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The update feature for Pydio Cells 2.0.4 allows an administrator user to set a custom update URL and the public RSA key used to validate the downloaded update package. The update process involves downloading the updated binary file from a URL indicated in the update server response, validating its checksum and signature with the provided public key and finally replacing the current application binary. To complete the update process, the application’s service or appliance needs to be restarted. An attacker with administrator access can leverage the software update feature to force the application to download a custom binary that will replace current Pydio Cells binary. When the server or service is eventually restarted the attacker will be able to execute code under the privileges of the user running the application. In the Pydio Cells enterprise appliance this is with the privileges of the user named “pydio”.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2020-12852","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-12853"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-12851"},"products":["n/a"],"published":"2020-06-04","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-32749","kev_date_added":null,"published":"2023-06-08"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2019-12901","kev_date_added":null,"published":"2019-06-19"},{"cvss_score":8.1,"headline":"Path traversal in n/a","id":"CVE-2020-12851","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":7.2,"headline":"Command injection in n/a","id":"CVE-2020-12847","kev_date_added":null,"published":"2020-06-04"},{"cvss_score":7,"headline":"The following vulnerability applies only to the Pydio Cells Enterprise OVF version 2.0.4.","id":"CVE-2020-12850","kev_date_added":null,"published":"2020-06-11"},{"cvss_score":6.5,"headline":"Server-side request forgery in n/a","id":"CVE-2023-32750","kev_date_added":null,"published":"2023-06-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["n/a"]},"summary":"Administrators can exploit the update feature to replace the application binary with a malicious one, leading to remote code execution upon service restart.","url":"https://insights.sbomify.com/CVE-2020-12852/"}