CVE-2013-1361
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 Lenovo Thinkpad Bluetooth with Enhanced Data Rate Software 6.4.0.2900 and earlier allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse DLL that is located in the same folder as a file that is processed by Lenovo Bluetooth.
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 confidenceLenovo Thinkpad Bluetooth with Enhanced Data Rate Software versions 6.4.0.2900 and earlier is vulnerable to DLL hijacking. The application loads dynamic link libraries from the same directory as files it processes without validating the DLL search path, allowing an attacker to place a malicious DLL in that location to achieve arbitrary code execution with the privileges of 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<= 6.4.0.2900CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 if Lenovo Thinkpad Bluetooth software is installedOpen Windows Control Panel > Programs and Features, or check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Thinkpad Bluetooth with Enhanced Data Rate Software' or similar Lenovo Bluetooth softwareAffected if The software is listed as installed on the system
-
Identify the installed version of the Bluetooth softwareIn Programs and Features, click on the Lenovo Bluetooth entry to view the version, or check the Version value in the registry key for that programAffected if The displayed version is 6.4.0.2900 or earlier
-
Verify the exact version number against the affected rangeCompare the installed version number to 6.4.0.2900 using standard version comparison (each numeric segment: major.minor.build.revision)Affected if The version is less than or equal to 6.4.0.2900 (e.g., 6.4.0.2900, 6.3.0.2800, 6.0.0.1000, etc.)
The system is affected if Lenovo Thinkpad Bluetooth with Enhanced Data Rate Software is installed and its version number is 6.4.0.2900 or earlier.
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 · scopedRemove or uninstall the vulnerable Lenovo Bluetooth software if not required, or apply any available vendor security updates. Ensure the application directory is not writable by untrusted users to prevent placement of malicious DLLs.
A newer version of Lenovo Thinkpad Bluetooth With Enhanced Data Rate Software (version > 6.4.0.2900)
- 1. Identify the current version of Lenovo Thinkpad Bluetooth With Enhanced Data Rate Software installed on the system.
- 2. Navigate to the Lenovo support website or use Lenovo System Update to check for available software updates.
- 3. Download and install any available Bluetooth software updates that are newer than version 6.4.0.2900.
- 4. After updating, verify the new version number to confirm the patch was applied.
- 5. As a temporary mitigation, ensure the Bluetooth software executable is run from a directory where untrusted users cannot place files, and avoid opening files from untrusted or shared locations.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1361 — 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-2013-1361 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