{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20718 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20718 is a critical unsafe deserialization vulnerability in n/a, published on 15 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20718 and fix it if it is affected.\n\nWhat it is: CVE-2018-20718 is a critical unsafe deserialization vulnerability in n/a, published on 15 Jan 2019. 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-2018-20718 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-2018-20718/ (Markdown: https://insights.sbomify.com/CVE-2018-20718/index.md)","id":"CVE-2018-20718","markdown":"https://insights.sbomify.com/CVE-2018-20718/index.md","name":"CVE-2018-20718","record":{"aliases":["GHSA-qhmw-m62m-p9xh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Pydio file sharing","requires_auth":"none","summary":"An attacker can achieve code execution in Pydio by exploiting PHP object injection via stored preferences, requiring a public link or unprivileged account access.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pydio","vendor":"pydio"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"In Pydio before 8.2.2, an attack is possible via PHP Object Injection because a user is allowed to use the $phpserial$a:0:{} syntax to store a preference. An attacker either needs a \"public link\" of a file, or access to any unprivileged user account for creation of such a link.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-07-10","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-07-10T18:19:59Z","kind":"github_poc","ref":"https://github.com/us3r777/CVE-2018-20718","stars":3,"title":null}],"tier":"poc_unverified"},"has_fix":false,"headline":"Deserialization in n/a","id":"CVE-2018-20718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2018-20719"},"packages":[],"prev":{"headline":"PrestaShop PHP Object Injection","id":"CVE-2018-20717"},"products":["n/a"],"published":"2019-01-15","related":[{"cvss_score":9.8,"headline":"Command injection in Ajaxeplorer","id":"CVE-2013-4267","kev_date_added":null,"published":"2020-02-11"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2019-9642","kev_date_added":null,"published":"2019-06-05"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2015-3431","kev_date_added":null,"published":"2017-09-19"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2019-20452","kev_date_added":null,"published":"2020-03-17"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2019-20453","kev_date_added":null,"published":"2020-03-17"},{"cvss_score":7.7,"headline":"Server-side request forgery in n/a","id":"CVE-2019-15033","kev_date_added":null,"published":"2019-09-19"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can achieve code execution in Pydio by exploiting PHP object injection via stored preferences, requiring a public link or unprivileged account access.","url":"https://insights.sbomify.com/CVE-2018-20718/"}