{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15487 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15487 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15487 is a critical SQL injection vulnerability in n/a, published on 30 Sep 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-15487 and fix it if it is affected.\n\nWhat it is: CVE-2020-15487 is a critical SQL injection vulnerability in n/a, published on 30 Sep 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-15487 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-15487/ (Markdown: https://insights.sbomify.com/CVE-2020-15487/index.md)","id":"CVE-2020-15487","markdown":"https://insights.sbomify.com/CVE-2020-15487/index.md","name":"CVE-2020-15487","record":{"aliases":["GHSA-q5cw-4q48-3cxj"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Re:Desk helpdesk","requires_auth":"none","summary":"Unauthenticated attackers can exploit SQL injection to achieve remote code execution and gain administrative privileges in Re:Desk.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"re\\","vendor":"re-desk"}],"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-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Re:Desk 2.3 contains a blind unauthenticated SQL injection vulnerability in the getBaseCriteria() function in the protected/models/Ticket.php file. By modifying the folder GET parameter, it is possible to execute arbitrary SQL statements via a crafted URL. Unauthenticated remote command execution is possible by using this SQL injection to update certain database values, which are then executed by a bizRule eval() function in the yii/framework/web/auth/CAuthManager.php file. Resultant authorization bypass is also possible, by recovering or modifying password hashes and password reset tokens, allowing for administrative privileges to be obtained.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2020-15487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Re:Desk 2.3 allows insecure file upload.","id":"CVE-2020-15488"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-15486"},"products":["n/a"],"published":"2020-09-30","related":[{"cvss_score":7.5,"headline":"Re:Desk 2.3 allows insecure file upload.","id":"CVE-2020-15488","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2020-15849","kev_date_added":null,"published":"2020-09-30"}],"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":"Unauthenticated attackers can exploit SQL injection to achieve remote code execution and gain administrative privileges in Re:Desk.","url":"https://insights.sbomify.com/CVE-2020-15487/"}