dbcve.org
SeriesApplication · Nokia

CVE-2005-0681

MEDIUM · 5.0 CVSS v2.0 Published 2005-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Nokia Symbian 60 allows remote attackers to cause a denial of service (phone restart) via a Bluetooth nickname.

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 confidence

Nokia Symbian S60 devices contain a vulnerability in the Bluetooth stack where a remote attacker can cause a denial of service (phone restart) by sending a specially crafted Bluetooth nickname to the target device.

MitigationDisable Bluetooth when not in use and set device to non-discoverable mode. Replace end-of-life Symbian S60 devices with modern smartphones as no vendor patches are available for this 2005 vulnerability.

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
SeriesApplication
Affected:= 60

CVSS 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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device platform
    Determine if the device is a Nokia Series 60 (Symbian S60) smartphone. Check the device model and operating system information in the phone settings or product documentation.
    Affected if The device is a Nokia Series 60 (Symbian S60) phone.
  2. Verify Bluetooth is enabled
    Check the phone Bluetooth settings to see if the Bluetooth radio is currently turned on.
    Affected if Bluetooth is enabled on the device.
  3. Check Bluetooth discoverability mode
    Inspect the Bluetooth settings to determine if the device is set to discoverable or non-discoverable mode.
    Affected if The device is set to discoverable mode (visible to other Bluetooth devices).

The device is affected if it is a Nokia Series 60 (Symbian S60) device with Bluetooth enabled and set to discoverable mode, allowing a remote attacker to send a malicious Bluetooth nickname that causes a restart.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable Bluetooth when not in use and set device to non-discoverable mode. Replace end-of-life Symbian S60 devices with modern smartphones as no vendor patches are available for this 2005 vulnerability.

Fix this in Series Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-0681 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-0681 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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