dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2023-46566

HIGH · 7.5 CVSS v3.1 Published 2024-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 vulnerability in msoulier tftpy commit 467017b844bf6e31745138a30e2509145b0c529c allows a remote attacker to cause a denial of service via the parse function in the TftpPacketFactory class.

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

A buffer overflow vulnerability exists in the parse function of the TftpPacketFactory class in the msoulier tftpy library (commit 467017b). A remote attacker can send specially crafted TFTP packets to cause a denial of service by overflowing a buffer during packet parsing.

MitigationUpdate tftpy to a version after commit 467017b844bf6e31745138a30e2509145b0c529c that contains proper bounds checking in the TftpPacketFactory.parse function, or implement input validation to ensure packet fields do not exceed allocated buffer sizes.

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

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Identify if tftpy library is installed
    Run 'pip show tftpy' or check your project's requirements.txt/dependencies for the tftpy package
    Affected if tftpy is present in the environment
  2. Determine the installed tftpy version
    Run 'pip show tftpy' and note the Version field, or check git log if using source code
    Affected if Version is before the fix commit 467017b or version number is unknown/older than patched release
  3. Verify TftpPacketFactory.parse source code
    Locate the tftpy source and inspect the TftpPacketFactory class parse function for bounds checking on packet field lengths
    Affected if No bounds checking exists on packet field parsing, or the vulnerable commit 467017b is in use
  4. Check if TFTP service is exposed to network
    Review application configuration to determine if tftpy is running as a TFTP server or processing packets from untrusted network sources
    Affected if TFTP server is listening on network interfaces or processing packets from untrusted sources

Environment is affected if tftpy library is present, the installed version predates the fix commit, and the system processes TFTP packets from untrusted network sources.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update tftpy to a version after commit 467017b844bf6e31745138a30e2509145b0c529c that contains proper bounds checking in the TftpPacketFactory.parse function, or implement input validation to ensure packet fields do not exceed allocated buffer sizes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46566 — 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-2023-46566 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