CVE-2024-46480
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 · uneditedAn NTLM hash leak in Venki Supravizio BPM up to 18.0.1 allows authenticated attackers with Application Administrator access to escalate privileges on the underlying host system.
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 confidenceVenki Supravizio BPM versions up to 18.0.1 contain an NTLM hash leak vulnerability that allows authenticated users with Application Administrator privileges to obtain NTLM password hashes, which can then be cracked or used in relay attacks to escalate privileges to the underlying host system.
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<= 18.0.1CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify the installed Venki Supravizio BPM versionLocate the version information for your Venki Supravizio BPM installation. This is typically found in the product about page, installation directory metadata, or by querying the application administration interface for version details.Affected if The installed version is 18.0.1 or any earlier version (<= 18.0.1)
-
Verify if NTLM authentication is enabledExamine the Venki Supravizio BPM authentication configuration settings. Access the security or authentication settings panel in the administration console to determine which authentication protocols are active.Affected if NTLM authentication is listed as an enabled or available authentication method in the configuration
-
Confirm the presence of Application Administrator accountsReview the user role assignments within Venki Supravizio BPM. Navigate to the user management or roles administration section to identify accounts assigned the Application Administrator role.Affected if There exists at least one user account with Application Administrator privileges
-
Assess network exposure of SMB servicesReview network topology and firewall rules to determine if the Venki Supravizio BPM server has unrestricted SMB network access that could be leveraged for NTLM relay attacks.Affected if The server has open or accessible SMB ports (445/139) on network segments accessible to potentially malicious authenticated users
You are affected if your Venki Supravizio BPM installation is version 18.0.1 or lower, NTLM authentication is enabled, and users with Application Administrator privileges exist in the system.
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.
From vendor dataUpgrade Venki Supravizio BPM to a version beyond 18.0.1; if no patch is available, disable NTLM authentication in favor of Kerberos or modern authentication protocols and implement SMB signing to prevent relay attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46480 — 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-46480 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