CVE-2001-0101 Other in n/a
Critical 10.0
Published
Updated
Check this codebase for CVE-2001-0101 and fix it if it is affected.
What it is: CVE-2001-0101 is a critical vulnerability in n/a, published on 2 Feb 2001. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2001-0101 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-0101/ (Markdown: https://insights.sbomify.com/CVE-2001-0101/index.md)
A vulnerability in fetchmail's GSSAPI authentication command allows attackers to potentially compromise the email retrieval service.
- 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-0101?
CVE-2001-0101 is a critical vulnerability in n/a, published on 2 Feb 2001. It can be exploited over the network.
Official description
Vulnerability in fetchmail 5.5.0-2 and earlier in the AUTHENTICATE GSSAPI command.
Which versions are affected by CVE-2001-0101?
It affects 1 product.
Products include Fetchmail Fetchmail.
How do I fix CVE-2001-0101?
No fix has been published for CVE-2001-0101 yet. Limit exposure of the affected software until one is available.
Is CVE-2001-0101 being exploited?
There is no known exploitation of CVE-2001-0101 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-286v-p4r7-vj8x.