CVE-2008-1611 Stack-based buffer overflow in TFTP Server SP 1.4 for Windows allows remote attackers to cause a denial of service or execute arbitrary code
Critical 10.0
Published
Updated
Check this codebase for CVE-2008-1611 and fix it if it is affected.
What it is: CVE-2008-1611 is a critical vulnerability in n/a, published on 1 Apr 2008.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1611 exists.
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-2008-1611/ (Markdown: https://insights.sbomify.com/CVE-2008-1611/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2008-1611?
CVE-2008-1611 is a critical vulnerability in n/a, published on 1 Apr 2008.
Official description
Stack-based buffer overflow in TFTP Server SP 1.4 for Windows allows remote attackers to cause a denial of service or execute arbitrary code via a long filename in a read or write request.
Weakness: CWE-119
Which versions are affected by CVE-2008-1611?
It affects 1 product.
Products include Tftp-Server Winagents Tftp Server.
How do I fix CVE-2008-1611?
No fix has been published for CVE-2008-1611 yet. Limit exposure of the affected software until one is available.
Is CVE-2008-1611 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1611 exists.
Public exploit code: 1 Metasploit module, 3 Exploit-DB entries and 1 proofs of concept on GitHub.
Sources
Also known as GHSA-2r36-xf69-7v47.