CVE-2001-0477 Command injection in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2001-0477 and fix it if it is affected.
What it is: CVE-2001-0477 is a high-severity command injection vulnerability in n/a, published on 24 May 2001. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2001-0477 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-2001-0477/ (Markdown: https://insights.sbomify.com/CVE-2001-0477/index.md)
Remote attackers can execute arbitrary commands on WebCalendar installations, posing a critical risk to server integrity.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Over the internet
- Victim action needed
- Not stated
- Fix
- None listed
What is CVE-2001-0477?
CVE-2001-0477 is a high-severity command injection vulnerability in n/a, published on 24 May 2001. It can be exploited over the network.
Official description
Vulnerability in WebCalendar 0.9.26 allows remote command execution.
Which versions are affected by CVE-2001-0477?
It affects 1 product.
Products include Webcalendar Webcalendar.
How do I fix CVE-2001-0477?
No fix has been published for CVE-2001-0477 yet. Limit exposure of the affected software until one is available.
Upgrade, and pass arguments to programs as a list instead of through a shell. More about Command injection.
Is CVE-2001-0477 being exploited?
There is no known exploitation of CVE-2001-0477 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-c7h7-cjhx-gphr.