CVE-2001-0060 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2001-0060 and fix it if it is affected.
What it is: CVE-2001-0060 is a critical vulnerability in n/a, published on 7 May 2001. 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-2001-0060 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-0060/ (Markdown: https://insights.sbomify.com/CVE-2001-0060/index.md)
Attackers can execute arbitrary commands via a malformed ident username due to a format string vulnerability in stunnel.
- 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-2001-0060?
CVE-2001-0060 is a critical vulnerability in n/a, published on 7 May 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Format string vulnerability in stunnel 3.8 and earlier allows attackers to execute arbitrary commands via a malformed ident username.
Which versions are affected by CVE-2001-0060?
It affects 1 product.
Products include Stunnel Stunnel.
How do I fix CVE-2001-0060?
No fix has been published for CVE-2001-0060 yet. Limit exposure of the affected software until one is available.
Is CVE-2001-0060 being exploited?
There is no known exploitation of CVE-2001-0060 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2011-2940 Memory corruption in n/a
- CVE-2021-20230 Auth bypass in stunnel
- CVE-2008-2400 Unspecified vulnerability in stunnel before 4.23, when running as a service on Windows, allows local users to gain privileges via unknown attack vectors.
- CVE-2008-2420 Security feature bypass in n/a
- CVE-2013-1762 Integer overflow in n/a
Sources
Also known as GHSA-cpcw-2gx9-xcwx.