CVE-2023-47113
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 · uneditedBleachBit cleans files to free disk space and to maintain privacy. BleachBit for Windows up to version 4.4.2 is vulnerable to a DLL Hijacking vulnerability. By placing a DLL in the Folder c:\DLLs, an attacker can run arbitrary code on every execution of BleachBit for Windows. This issue has been patched in version 4.5.0.
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 confidenceBleachBit for Windows versions up to 4.4.2 are vulnerable to DLL hijacking. An attacker can place a malicious DLL in c:\DLLs, which gets loaded by BleachBit on execution, allowing arbitrary code execution with the privileges of the user running the application.
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.4.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 installed BleachBit versionOpen BleachBit, go to Help > About, or check the version displayed on the main window. Alternatively, right-click the BleachBit executable, select Properties, and check the Details tab for the version number.Affected if The installed version is 4.4.2 or lower (any version up to and including 4.4.2).
-
Verify c:\DLLs directory existsOpen File Explorer or command prompt and navigate to C:\DLLs, or run 'dir C:\DLLs' in cmd.exe.Affected if The directory C:\DLLs exists on the system.
-
List contents of c:\DLLs folderRun 'dir C:\DLLs' in command prompt or use File Explorer to view all files in C:\DLLs.Affected if Any DLL files are present in the C:\DLLs directory, especially unknown or untrusted ones.
-
Identify source of DLLs in c:\DLLsReview the DLL file properties (right-click > Properties > Details) to determine if the DLLs are from trusted sources or were placed by an untrusted party.Affected if DLLs in C:\DLLs are from unknown, untrusted, or suspicious sources.
You are affected if BleachBit version 4.4.2 or lower is installed AND the C:\DLLs directory exists with any DLL files present, particularly untrusted ones that could be exploited for arbitrary code execution.
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 · scopedUpgrade to BleachBit version 4.5.0 or later. As a temporary workaround, ensure the c:\DLLs folder does not contain any untrusted DLLs and that the application is run from trusted locations only.
BleachBit 4.5.0 or later
- Download BleachBit version 4.5.0 or later from the official BleachBit GitHub repository or website
- Uninstall the current vulnerable version of BleachBit (4.4.2 or earlier)
- Install the new version (4.5.0 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47113 — 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-47113 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