CVE-2024-57049 DO NOT USE THIS CVE RECORD.
Not scored
Published
Updated
Check this codebase for CVE-2024-57049 and fix it if it is affected.
What it is: CVE-2024-57049 is a vulnerability, published on 18 Feb 2025.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57049 exists.
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-2024-57049/ (Markdown: https://insights.sbomify.com/CVE-2024-57049/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2024-57049?
CVE-2024-57049 is a vulnerability, published on 18 Feb 2025.
Official description
DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Which versions are affected by CVE-2024-57049?
How do I fix CVE-2024-57049?
No fix has been published for CVE-2024-57049 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-57049 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-57049 exists.
Public exploit code: 1 Nuclei template.
Sources
Also known as GHSA-qr32-fcm4-m5h9.