dbcve.org
Tftp HpaApplication · H Peter Anvin

CVE-2011-2199

HIGH · 7.5 CVSS v2.0 Published 2012-07-22
Fix available
A fix is available. Upgrade to after 5.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer overflow in tftp-hpa before 5.1 allows remote attackers to cause a denial of service and possibly execute arbitrary code via the utimeout option.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Buffer overflow vulnerability in tftp-hpa versions before 5.1 allows remote attackers to trigger the issue via a specially crafted utimeout option in TFTP requests. The overflow occurs due to insufficient bounds checking when processing the utimeout option value, potentially enabling denial of service or arbitrary code execution.

MitigationUpgrade tftp-hpa to version 5.1 or later which contains the patch. If upgrading is not immediately feasible, consider firewall rules restricting TFTP access to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tftp HpaApplication
Affected:<= 5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if tftp-hpa package is installed
    On RHEL/CentOS: rpm -qa | grep tftp-hpa. On Debian/Ubuntu: dpkg -l | grep tftp-hpa. Or use: which tftpd
    Affected if The package is installed and the version displayed is 5.0 or lower, or no version is shown (indicating an old unpatched build)
  2. Check tftp server version directly
    Run: tftp-hpa --version or tftpd --version
    Affected if The version shown is 5.0 or earlier, or the command fails indicating an unpatched installation
  3. Verify if TFTP server daemon is running
    Run: ps aux | grep -E 'tftp|tftpd' or check systemctl status tftp.service / xinetd if TFTP is configured via xinetd
    Affected if A tftpd process is actively running and accepting connections, making the vulnerable code path accessible to network requesters
  4. Check TFTP service listener
    Run: netstat -tulpn | grep :69 or ss -tulpn | grep :69
    Affected if Port 69 (TFTP) is listening and accepting connections, confirming the attack surface is exposed

If tftp-hpa version 5.0 or lower is installed AND the TFTP server daemon is running and network-accessible, the environment is vulnerable to CVE-2011-2199.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 5.0
Interim mitigation

Upgrade tftp-hpa to version 5.1 or later which contains the patch. If upgrading is not immediately feasible, consider firewall rules restricting TFTP access to trusted sources only.

Fix this in Tftp Hpa Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-2199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-2199 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data