{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-51803 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-51803 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-51803 is a critical vulnerability in n/a, published on 31 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-51803 and fix it if it is affected.\n\nWhat it is: CVE-2023-51803 is a critical vulnerability in n/a, published on 31 Mar 2024. 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-2023-51803 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-2023-51803/ (Markdown: https://insights.sbomify.com/CVE-2023-51803/index.md)","id":"CVE-2023-51803","markdown":"https://insights.sbomify.com/CVE-2023-51803/index.md","name":"CVE-2023-51803","record":{"aliases":["GHSA-7822-f4vj-qh7p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Heimdall dashboard","requires_auth":"none","summary":"Attackers can upload malicious files containing PHP code disguised as icons, potentially leading to remote code execution on the Heimdall dashboard.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-674","name":"Uncontrolled Recursion"}],"description":"LinuxServer.io Heimdall before 2.5.7 does not prevent use of icons that have non-image data such as the \"\u003c?php ?\u003e\" substring.","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":"File upload in n/a","id":"CVE-2023-51803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2023-51804"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-51802"},"products":["n/a"],"published":"2024-03-31","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-20","vendors":["n/a"]},"summary":"Attackers can upload malicious files containing PHP code disguised as icons, potentially leading to remote code execution on the Heimdall dashboard.","url":"https://insights.sbomify.com/CVE-2023-51803/"}