CVE-2020-25174
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 DLL hijacking vulnerability in the B. Braun OnlineSuite Version AP 3.0 and earlier allows local attackers to execute code on the system as a high privileged user.
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 in B. Braun OnlineSuite AP 3.0 and earlier allows local attackers to place malicious DLLs in directories searched by the application, resulting in code execution with high-privileged user context.
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<= 3.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.
-
Identify if B. Braun OnlineSuite is installedCheck common installation paths such as C:\Program Files\B Braun\, C:\Program Files (x86)\B Braun\, or look in Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\B Braun or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\B Braun for the OnlineSuite keyAffected if The application is found on the system
-
Determine the installed versionCheck the version information of the OnlineSuite executable (typically named OnlineSuite.exe or similar) by right-clicking the file, selecting Properties, and viewing the Details tab, or use command: dir "C:\Program Files\B Braun\*" /s /b or registry query at HKLM\SOFTWARE\B Braun\OnlineSuite for a Version valueAffected if The version is 3.0 or earlier, or if no version information is found and the product appears to be the legacy OnlineSuite application
-
Identify DLL search path directories used by the applicationUse Process Monitor or examine the application installation directory structure to identify folders where the application loads DLLs from. Common paths include the application root, System32, Windows, current working directory, and PATH directoriesAffected if The application loads DLLs from directories writable by lower-privilege users
-
Check directory permissions for DLL planting riskRight-click each directory in the application DLL search path, select Properties, then Security tab. Verify that non-admin users or the Users group do not have Write or Write & Execute permissions on these directoriesAffected if Any directory in the DLL search path allows write access to non-privileged users, enabling them to place malicious DLLs that the application will load
A user is affected if B. Braun OnlineSuite AP version 3.0 or earlier is installed AND any directory in its DLL search path is writable by non-privileged users, allowing 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.
From vendor dataApply vendor patch when available. If no patch exists, restrict write permissions on application directories in the DLL search path and modify the application to use safe DLL loading APIs with explicit paths.
- 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-2020-25174 — 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-2020-25174 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