CVE-2018-0692
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 · uneditedUntrusted search path vulnerability in Baidu Browser Version 43.23.1000.500 and earlier allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
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 confidenceDLL hijacking vulnerability in Baidu Browser allows attackers to place malicious DLL files in an unspecified directory that the browser searches for DLLs, enabling arbitrary code execution with the privileges of the user running the browser.
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<= 43.23.1000.500CVSS 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.0/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.
-
Confirm Baidu Spark Browser is installedLook for Baidu Spark Browser in the system: Check C:\Program Files\Baidu or C:\Program Files (x86)\Baidu for the Spark folder, or search for 'Spark' in Add/Remove Programs or Programs and Features.Affected if Baidu Spark Browser is found on the system.
-
Identify installed Baidu Spark Browser versionNavigate to the Baidu Spark Browser installation folder (typically C:\Program Files\Baidu\Spark or C:\Program Files (x86)\Baidu\Spark), right-click the executable file (such as spark.exe or SSpark.exe), select Properties, and view the version number on the Details tab.Affected if The displayed version is 43.23.1000.500 or earlier.
-
Check DLL search path behaviorRun Baidu Spark Browser while monitoring DLL loading using tools such as Process Monitor (procmon.exe from Sysinternals) to observe which directories the browser searches for DLL files. Filter by process name and look for DLL load events that reference directories outside the browser's own folder.Affected if The browser loads DLLs from directories accessible to untrusted users, or the DLL search path includes user-writable locations.
-
Review file system permissions on browser directoryRight-click the Baidu Spark Browser installation folder, select Properties, go to the Security tab, and verify which users have Write or Modify permissions on the folder. Also check system PATH directories for write access by untrusted users.Affected if The browser installation directory or any PATH directories are writable by users who should not have elevated access.
A user is affected if Baidu Spark Browser version 43.23.1000.500 or earlier is installed and the browser's DLL search path includes directories 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 dataUpdate Baidu Browser to a version later than 43.23.1000.500, or replace with an alternative browser. As a defensive measure, ensure the browser installation directory and system PATH directories are not writable by untrusted users.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0692 — 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-2018-0692 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