RedisDatabase / datastore
CVE-2022-3734
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 · uneditedA vulnerability was found in a port or fork of Redis. It has been declared as critical. This vulnerability affects unknown code in the library C:/Program Files/Redis/dbghelp.dll. The manipulation leads to uncontrolled search path. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The identifier of this vulnerability is VDB-212416. NOTE: The official Redis release is not affected. This issue might affect an unofficial fork or port on Windows only.
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 confidenceA DLL hijacking vulnerability exists in Windows-based Redis ports/forks where the application loads dbghelp.dll from an uncontrolled search path. An attacker with local access could place a malicious DLL in a location where Redis would load it, potentially achieving code execution with elevated privileges.
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
RedisDatabase / datastore
all versionsCVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 Windows environmentVerify the operating system is Windows (uname -s or systeminfo)Affected if Running on Windows exposes the DLL hijacking attack surface
-
Identify Redis implementationCheck if running official Redis or a fork (redis-server --version, examine process name, check installation source)Affected if Using an unofficial Redis fork on Windows is potentially affected; official Redis is not vulnerable
-
Check for dbghelp.dll in Redis directoryList files in the Redis installation directory for dbghelp.dllAffected if dbghelp.dll present in Redis directory indicates vulnerable configuration
-
Inspect DLL loading behaviorUse Process Monitor or similar tool to observe which dbghelp.dll Redis loads and from which path during startup or when debug features are usedAffected if Redis loads dbghelp.dll from a user-controlled or uncontrolled directory path
User is affected only if running an unofficial Redis fork on Windows that loads dbghelp.dll from an uncontrolled search path, allowing local privilege escalation via DLL hijacking
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 · scopedIf using an unofficial Redis fork on Windows, audit DLL loading behavior, use absolute paths for dependencies, remove unnecessary DLL dependencies, or migrate to the official Redis release which is not affected.
- This CVE does not affect official Redis releases. The vulnerability description explicitly states: 'The official Redis release is not affected' and 'This issue might affect an unofficial fork or port on Windows only'.
- If you are using an unofficial Windows port or fork of Redis, discontinue use and switch to the official Redis release from redis.io or your system's official package manager.
- If you must use a Windows port, verify the source and build configuration of the dbghelp.dll to ensure it is loaded from a secure, trusted path.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Redis
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3734 — 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-3734 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