CVE-2024-36451
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 · uneditedImproper handling of insufficient permissions or privileges vulnerability exists in ajaxterm module of Webmin prior to 2.003. If this vulnerability is exploited, a console session may be hijacked by an unauthorized user. As a result, data within a system may be referred, a webpage may be altered, or a server may be permanently halted.
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 confidenceA privilege handling vulnerability in Webmin's ajaxterm module prior to version 2.003 allows unauthorized users to hijack console sessions. The improper permission checks enable attackers to gain unauthorized access to terminal sessions, potentially leading to data exfiltration, web tampering, or service disruption.
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< 2.003CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Webmin is runningCheck for running Webmin service: systemctl status webmin or ps aux | grep miniservAffected if Webmin service is not found or not running - still check version for completeness
-
Identify installed Webmin versionRun: cat /usr/libexec/webmin/version or look for version file in Webmin installation directory (typically /usr/libexec/webmin/)Affected if Version file shows version < 2.003 or version cannot be determined (treat as potentially vulnerable)
-
Check ajaxterm module statusLook for ajaxterm in Webmin's module directory (typically /usr/libexec/webmin/ajaxterm/) and verify it is not disabled or removedAffected if ajaxterm directory exists and module is enabled - vulnerability is present if version is < 2.003
-
Verify ajaxterm endpoint accessibilityCheck Webmin configuration for ajaxterm-related URL handlers in /etc/webmin/config or via Webmin's ACL settings. Confirm the endpoint responds without proper authorizationAffected if ajaxterm endpoint is accessible without elevated privileges or proper session validation
If Webmin version is below 2.003 and the ajaxterm module is present and enabled, the environment is affected by CVE-2024-36451.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.003
Update Webmin to version 2.003 or later to patch the ajaxterm module's privilege handling vulnerability. If immediate update is not feasible, consider restricting access to the ajaxterm endpoint via network controls or authentication mechanisms.
Webmin 2.003
- Backup current Webmin configuration and data
- Check current Webmin version
- Upgrade Webmin to version 2.003 or later
- Restart Webmin services if required
- Verify the ajaxterm module functions correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36451 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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