CVE-2022-23410
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 · uneditedAXIS IP Utility before 4.18.0 allows for remote code execution and local privilege escalation by the means of DLL hijacking. IPUtility.exe would attempt to load DLLs from its current working directory which could allow for remote code execution if a compromised DLL would be placed in the same folder.
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 confidenceAXIS IP Utility before version 4.18.0 contains a DLL hijacking vulnerability where IPUtility.exe loads dynamic-link libraries from its current working directory instead of using secure, absolute paths. An attacker who can place a malicious DLL in the same directory as IPUtility.exe can achieve remote code execution or local privilege escalation when the application runs.
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< 4.18.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Locate IPUtility.exe and identify its versionFind IPUtility.exe on the system (commonly in C:\Program Files\AXIS IP Utility or similar), right-click the file, select Properties, and view the Details tab to see the File VersionAffected if The version displayed is blank or shows a version number less than 4.18.0
-
Verify the exact version number against the affected rangeCompare the found version number to the vulnerable range: any version before 4.18.0 is affectedAffected if The version is 4.17.x, 4.16.x, or any earlier version, or if no version information is displayed in the file properties
-
Identify the directory where IPUtility.exe residesNote the full path of the folder containing IPUtility.exe as shown in Windows Explorer address bar or File ExplorerAffected if IPUtility.exe is located in a directory where non-privileged users have write access, such as a shared network folder, user desktop, or downloads folder
-
Check directory write permissionsRight-click the containing folder, select Properties, go to the Security tab, and verify which users or groups have Write permission to that folderAffected if Users other than Administrators or the system account have Write permission to the folder containing IPUtility.exe
The environment is affected if the installed AXIS IP Utility version is before 4.18.0 and the application is run from a directory where an attacker could place a malicious DLL file.
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 · scoped4.18.0
Upgrade AXIS IP Utility to version 4.18.0 or later to obtain the vendor patch. Additionally, ensure the application is run from a secure directory with restricted write access to prevent placement of malicious DLLs.
AXIS IP Utility 4.18.0 or later
- Navigate to the official AXIS website at www.axis.com
- Locate the AXIS IP Utility download page
- Download version 4.18.0 or later of AXIS IP Utility
- Run the installer with administrator privileges
- Follow the installation wizard prompts to complete the upgrade
- Verify the installed version matches the fixed release (4.18.0 or newer)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23410 — 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-2022-23410 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