dbcve.org
VirtualminApplication

CVE-2024-45692

HIGH · 7.5 CVSS v3.1 Published 2024-09-04
Fix available
A fix is available. Upgrade to 2.202 / 7.20.2 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
Webmin before 2.202 and Virtualmin before 7.20.2 allow a network traffic loop via spoofed UDP packets on port 10000.

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 · high confidence

Webmin before version 2.202 and Virtualmin before version 7.20.2 contain a vulnerability where an attacker can send spoofed UDP packets to port 10000 (the default Webmin management port), causing a network traffic loop that can lead to denial of service through excessive bandwidth consumption.

MitigationUpdate Webmin to version 2.202 or later and Virtualmin to version 7.20.2 or later. Additionally, implement network-level ingress filtering (uRPF, ACLs) to block spoofed UDP packets at the network perimeter.

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
VirtualminApplication
Affected:< 7.20.2
WebminApplication
Affected:< 2.202

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. Check Webmin version
    Run 'rpm -q webmin' or 'dpkg -l webmin' to get the installed package version, or access Webmin UI and check the 'Webmin > Webmin Configuration > About Webmin' page for the version number
    Affected if The installed version is lower than 2.202 (e.g., 2.201, 2.200, etc.)
  2. Check Virtualmin version
    Run 'rpm -q virtualmin' or 'dpkg -l virtualmin' to get the installed package version, or check Virtualmin UI under 'Virtualmin > System Information' for the version
    Affected if The installed version is lower than 7.20.2 (e.g., 7.20.1, 7.20.0, etc.)
  3. Verify UDP port 10000 is listening
    Run 'ss -ulnp | grep 10000' or 'netstat -ulnp | grep 10000' to check if Webmin's UDP port is open and listening
    Affected if UDP port 10000 is in LISTEN state and bound to a network interface (especially 0.0.0.0 or external IP)
  4. Check network exposure of port 10000
    Run 'iptables -L -n | grep 10000' or 'ufw status' to see if there are firewall rules allowing UDP traffic on port 10000 from untrusted networks
    Affected if Port 10000 UDP is permitted through the firewall for external sources (not restricted to localhost or VPN-only)
  5. Check for spoofed packet filtering
    Review network device configurations (router/switch) for anti-spoofing measures such as uRPF (Unicast Reverse Path Forwarding) or ingress ACLs that block packets with spoofed source IPs
    Affected if No anti-spoofing filters are in place at the network perimeter and the system is internet-facing on port 10000

You are affected if Webmin is below version 2.202 or Virtualmin is below version 7.20.2, UDP port 10000 is exposed to untrusted networks, and anti-spoofing filtering is not implemented at the network edge.

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.

dbcve · scoped
Upgrade available Upgrade to 2.202 / 7.20.2 or later
Fixed in 2.2027.20.2
Interim mitigation

Update Webmin to version 2.202 or later and Virtualmin to version 7.20.2 or later. Additionally, implement network-level ingress filtering (uRPF, ACLs) to block spoofed UDP packets at the network perimeter.

Recommended fix High confidence

Webmin >= 2.202 or Virtualmin >= 7.20.2

  1. Identify whether you are running Webmin or Virtualmin (or both)
  2. For Webmin: Upgrade to version 2.202 or later using your system's package manager or Webmin's built-in update feature
  3. For Virtualmin: Upgrade to version 7.20.2 or later using your system's package manager or Virtualmin's built-in update feature
  4. After upgrade, verify the version by checking the Webmin/Virtualmin dashboard or running 'webmin --version'
  5. Verify the service is running correctly and accessible on port 10000

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

Fix this in Virtualmin Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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