dbcve.org
Bloxone EndpointApplication · Infoblox

CVE-2022-32972

HIGH · 7.8 CVSS v3.1 Published 2023-02-17
Fix available
A fix is available. Upgrade to 2.3.3 or later.
See remediation →
80/100
Remediation priority · High
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
Infoblox BloxOne Endpoint for Windows through 2.2.7 allows DLL injection that can result in local privilege escalation.

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

Infoblox BloxOne Endpoint for Windows versions through 2.2.7 contains a DLL injection vulnerability that allows a local attacker to inject malicious DLLs into the application process, leading to privilege escalation from standard user to administrator or system-level privileges.

MitigationUpgrade Infoblox BloxOne Endpoint for Windows to a version newer than 2.2.7 once the vendor releases a patch, or apply vendor-supplied remediation. As a temporary workaround, ensure strict access controls on the application directory and monitor for unauthorized DLL placement.

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
Bloxone EndpointApplication
Affected:< 2.3.3

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

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Infoblox BloxOne Endpoint is installed
    Check Windows installed programs list (Programs and Features) or registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Infoblox BloxOne Endpoint' or similar
    Affected if The application appears in the installed programs list
  2. Determine the installed version
    Locate the BloxOne Endpoint installation directory (commonly under C:\Program Files\Infoblox or C:\Program Files (x86)\Infoblox) and check the version information of the main executable, or view the version in the uninstall registry entry
    Affected if The version shown is lower than 2.3.3 (versions through 2.2.7 are affected)
  3. Confirm vulnerability applicability
    If the application is installed and version is below 2.3.3, the environment falls within the affected version range
    Affected if Installed version is less than 2.3.3
  4. Inspect application directory permissions
    Right-click the installation directory, go to Properties > Security, and verify which users have Write or Modify permissions to the folder
    Affected if Standard users or unauthorized accounts have Write access to the application directory, allowing DLL injection
  5. Scan for unauthorized DLL files
    Examine the application installation folder for any unexpected or recently added DLL files that do not belong to the original installation
    Affected if Unexpected DLL files are present in the application directory

The environment is affected if Infoblox BloxOne Endpoint for Windows is installed with a version lower than 2.3.3 and the application directory permits write access to non-admin users.

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.3.3 or later
Fixed in 2.3.3
Interim mitigation

Upgrade Infoblox BloxOne Endpoint for Windows to a version newer than 2.2.7 once the vendor releases a patch, or apply vendor-supplied remediation. As a temporary workaround, ensure strict access controls on the application directory and monitor for unauthorized DLL placement.

Recommended fix Moderate confidence

Bloxone Endpoint 2.3.3 or later

  1. Verify current Bloxone Endpoint version by checking Add/Remove Programs or the Bloxone Endpoint client interface
  2. Download Bloxone Endpoint version 2.3.3 or later from the Infoblox support portal or official distribution channels
  3. Create a backup of current Bloxone Endpoint configuration if applicable
  4. Uninstall the current Bloxone Endpoint version from the Windows system
  5. Install the updated Bloxone Endpoint version 2.3.3 or later
  6. Verify the installation completed successfully
  7. Restart the Windows system if required by the installer
  8. Confirm the new version is reflected in the client interface and Add/Remove Programs
Caveat Review Infoblox release notes for any configuration or behavioral changes between your current version and 2.3.3; test in non-production environment first if possible

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

Fix this in Bloxone Endpoint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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