CVE-2009-0671 Format string vulnerability in the University of Washington (UW) c-client library, as used by the UW IMAP toolkit imap-2007d and other appli
Not scored
Published
Updated
Check this codebase for CVE-2009-0671 and fix it if it is affected.
What it is: CVE-2009-0671 is a vulnerability, published on 22 Feb 2009.
Exploitation: There is no known exploitation of CVE-2009-0671 in the wild and no public exploit code.
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-2009-0671/ (Markdown: https://insights.sbomify.com/CVE-2009-0671/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2009-0671?
CVE-2009-0671 is a vulnerability, published on 22 Feb 2009.
Official description
Format string vulnerability in the University of Washington (UW) c-client library, as used by the UW IMAP toolkit imap-2007d and other applications, allows remote attackers to execute arbitrary code via format string specifiers in the initial request to the IMAP port (143/tcp). NOTE: Red Hat has disputed the vulnerability, stating "The Red Hat Security Response Team have been unable to confirm the existence of this format string vulnerability in the toolkit, and the sample published exploit is not complete or functional." CVE agrees that the exploit contains syntax errors and uses Unix-only include files while invoking Windows functions
Which versions are affected by CVE-2009-0671?
How do I fix CVE-2009-0671?
No fix has been published for CVE-2009-0671 yet. Limit exposure of the affected software until one is available.
Is CVE-2009-0671 being exploited?
There is no known exploitation of CVE-2009-0671 in the wild and no public exploit code.