CVE-2023-51803 File upload in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2023-51803 and fix it if it is affected.
What 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.
Exploitation: There is no known exploitation of CVE-2023-51803 in the wild and no public exploit code.
Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2023-51803/ (Markdown: https://insights.sbomify.com/CVE-2023-51803/index.md)
Attackers can upload malicious files containing PHP code disguised as icons, potentially leading to remote code execution on the Heimdall dashboard.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-51803?
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.
Official description
LinuxServer.io Heimdall before 2.5.7 does not prevent use of icons that have non-image data such as the "<?php ?>" substring.
Weakness: CWE-674
Which versions are affected by CVE-2023-51803?
How do I fix CVE-2023-51803?
No fix has been published for CVE-2023-51803 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-51803 being exploited?
There is no known exploitation of CVE-2023-51803 in the wild and no public exploit code.
Sources
Also known as GHSA-7822-f4vj-qh7p.