CVE-2023-3091
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** UNSUPPORTED WHEN ASSIGNED ** A vulnerability was found in Captura up to 8.0.0. It has been declared as critical. This vulnerability affects unknown code in the library CRYPTBASE.dll. The manipulation leads to uncontrolled search path. Attacking locally is a requirement. The complexity of an attack is rather high. The exploitation appears to be difficult. The identifier of this vulnerability is VDB-230668. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
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 (uncontrolled search path) exists in Captura up to version 8.0.0 within the CRYPTBASE.dll library. The application loads DLLs from locations that can be manipulated by a local attacker, potentially allowing execution of malicious code. This is a local attack requiring high complexity and is difficult to exploit.
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<= 8.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Captura is installedSearch for Captura in standard installation directories (C:\Program Files\Captura, C:\Program Files (x86)\Captura) or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Captura entriesAffected if Captura is found installed on the system
-
Determine installed Captura versionCheck the executable properties of Captura.exe (right-click > Properties > Details) or look for a version entry in the installation directory or uninstall registry keyAffected if The version is 8.0.0 or any version lower than 8.0.0
-
Locate CRYPTBASE.dll in application directoryBrowse to the Captura installation directory and verify if CRYPTBASE.dll file exists alongside the main executableAffected if CRYPTBASE.dll is present in the Captura installation folder
-
Inspect DLL search path vulnerabilityUse Process Monitor (procmon) from Sysinternals to capture DLL load events when launching Captura.exe, filtering for DLL names and checking for loads from user-writable directories outside the application folderAffected if Captura loads DLLs from directories with weak permissions or user-controlled paths
-
Verify directory permissions on Captura folderRight-click the Captura installation directory > Properties > Security, and check if standard users or low-privilege accounts have write/modify permissions to the folderAffected if Non-admin users have write access to the Captura installation directory, allowing DLL injection
A system is affected if Captura version 8.0.0 or lower is installed with CRYPTBASE.dll present and the application directory or its parent paths are writable by untrusted users.
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 dataSince Captura is unsupported, discontinue use if possible. If continued use is required, implement restrictive file permissions on the application directory, use application whitelisting, and ensure the application runs from a trusted directory to prevent DLL injection. Alternatively, recompile the application with secure DLL loading practices (explicit paths, Safe DLL Search Mode disabled).
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3091 — 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-2023-3091 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