CVE-2024-33393 Privilege escalation in n/a
Medium 6.2
Published
Updated
Check this codebase for CVE-2024-33393 and fix it if it is affected.
What it is: CVE-2024-33393 is a medium-severity vulnerability in n/a, published on 1 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33393 exists.
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-2024-33393/ (Markdown: https://insights.sbomify.com/CVE-2024-33393/index.md)
A local attacker can execute arbitrary code and escalate privileges by sending a crafted command to the token component in Spiderpool.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-33393?
CVE-2024-33393 is a medium-severity vulnerability in n/a, published on 1 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
An issue in spidernet-io spiderpool v.0.9.3 and before allows a local attacker to execute arbitrary code via a crafted command to get the token component.
Which versions are affected by CVE-2024-33393?
How do I fix CVE-2024-33393?
No fix has been published for CVE-2024-33393 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-33393 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-33393 exists.
Sources
Also known as GHSA-v7jc-fx5p-2j4v.