CVE-2022-23748
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 · uneditedmDNSResponder.exe is vulnerable to DLL Sideloading attack. Executable improperly specifies how to load the DLL, from which folder and under what conditions. In these scenarios, a malicious attacker could be using the valid and legitimate executable to load malicious files.
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 confidencemDNSResponder.exe has a DLL sideloading vulnerability where it does not properly specify full paths for DLL loading, allowing attackers to place a malicious DLL in a directory that gets searched before the legitimate DLL location. When the executable runs, it loads the attacker's DLL instead of the intended one, enabling code execution in the context of the legitimate process.
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<= 1.2.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.
-
Check if Audinate Dante Application Library is installedOpen Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs and look for 'Audinate Dante Application Library' or 'Dante'Affected if The program is listed with a version number less than or equal to 1.2.0
-
Locate mDNSResponder.exe on the systemSearch for the file using 'Get-ChildItem -Path C:\ -Filter mDNSResponder.exe -Recurse -ErrorAction SilentlyContinue' in PowerShell, or check typical installation paths like C:\Program Files\Audinate\Dante\Affected if mDNSResponder.exe is found on the system alongside the affected Dante Application Library
-
Check if mDNSResponder.exe resides in a directory with weak permissionsRight-click the directory containing mDNSResponder.exe, go to Properties > Security, and verify whether standard users or the Everyone group have Write or Modify permissions on that folderAffected if Users other than Administrators can write files to the folder where mDNSResponder.exe is located, allowing placement of malicious DLLs
-
Examine the DLL search path behaviorUse Process Monitor from Sysinternals to capture DLL load events for mDNSResponder.exe, or run 'dumpbin /dependents mDNSResponder.exe' if available from Visual Studio tools to list DLL dependenciesAffected if The executable loads DLLs from the current working directory, same directory as the executable, or system paths without using absolute paths
If Audinate Dante Application Library version 1.2.0 or lower is installed with mDNSResponder.exe present in a writable directory, the environment is vulnerable to CVE-2022-23748.
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 dataEnsure only privileged administrators can write to directories in the DLL search path for mDNSResponder.exe, or recompile the executable to use explicit absolute paths for DLL loading to prevent search order hijacking.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23748 — 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-23748 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