CVE-2005-3102 File upload in n/a
Medium 5.0
Published
Updated
Check this codebase for CVE-2005-3102 and fix it if it is affected.
What it is: CVE-2005-3102 is a medium-severity vulnerability in n/a, published on 28 Sep 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3102 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-2005-3102/ (Markdown: https://insights.sbomify.com/CVE-2005-3102/index.md)
Attackers with administrative access can upload files with arbitrary extensions to the web root, potentially leading to remote code execution.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2005-3102?
CVE-2005-3102 is a medium-severity vulnerability in n/a, published on 28 Sep 2005. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
The administrative interface in Movable Type allows attackers to upload files with arbitrary extensions under the web root.
Which versions are affected by CVE-2005-3102?
How do I fix CVE-2005-3102?
No fix has been published for CVE-2005-3102 yet. Limit exposure of the affected software until one is available.
Is CVE-2005-3102 being exploited?
There is no known exploitation of CVE-2005-3102 in the wild and no public exploit code.
Sources
Also known as GHSA-g9xr-g64h-jcj5.