dbcve.org
FedoraOperating system · Fedoraproject

CVE-2023-29483

HIGH · 7.0 CVSS v3.1 Published 2024-04-11
Fix available
A fix is available. Upgrade to 0.35.2 / 2.6.0 or later.
See remediation →
79/100
Remediation priority · High
Public exploit 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
eventlet before 0.35.2, as used in dnspython before 2.6.0, allows remote attackers to interfere with DNS name resolution by quickly sending an invalid packet from the expected IP address and source port, aka a "TuDoor" attack. In other words, dnspython does not have the preferred behavior in which the DNS name resolution algorithm would proceed, within the full time window, in order to wait for a valid packet. NOTE: dnspython 2.6.0 is unusable for a different reason that was addressed in 2.6.1.

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

A detailed technical summary for this CVE is being prepared.

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
FedoraOperating system
Affected:= 38= 39= 40
EventletApplication
Affected:< 0.35.2
DnspythonApplication
Affected:< 2.6.0
Bootstrap OsOperating system
Affected:all versions

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

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

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.

dbcve · scoped
Upgrade available Upgrade to 0.35.2 / 2.6.0 or later
Fixed in 0.35.22.6.0
Recommended fix High confidence

dnspython >= 2.6.1, eventlet >= 0.35.2

  1. Upgrade dnspython to version 2.6.1 or later to address the TuDoor vulnerability and the usability issue in 2.6.0
  2. If using eventlet, upgrade eventlet to version 0.35.2 or later as it is a dependency that contains the fix
  3. For Fedora systems, run 'dnf update dnspython' and 'dnf update python-eventlet' to apply the patched packages
  4. Verify the fix by checking that DNS resolution behavior now waits for valid packets within the full time window rather than being susceptible to early invalid packet injection
  5. Alternatively, reinstall or pin the updated packages: pip install --upgrade 'dnspython>=2.6.1' 'eventlet>=0.35.2'
Caveat Note that dnspython 2.6.0 had usability issues that were addressed in 2.6.1; ensure application compatibility with 2.6.1 changes

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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