CVE-2005-2182
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 · uneditedGrandstream BudgeTone (BT) 100 Voice over IP (VoIP) phones do not properly check the Call-ID, branch, and tag values in a NOTIFY message to verify a subscription, which allows remote attackers to spoof messages such as the "Messages waiting" message.
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 confidenceThe Grandstream BudgeTone 100 VoIP phone fails to validate Call-ID, branch, and tag parameters in incoming SIP NOTIFY messages, allowing remote attackers to spoof subscription-related notifications such as 'Messages waiting' by sending malicious NOTIFY requests without proper session binding verification.
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 dataall versionsCVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 the device modelAccess the device's web administration interface or check the physical device label for the exact model number. Look for 'Grandstream BudgeTone 100' or 'BT 100' marking.Affected if The device is a Grandstream BudgeTone 100 VoIP phone (any firmware version)
-
Check if SIP is enabledLog into the device's web interface and navigate to the SIP settings or account configuration section. Verify if SIP functionality is turned on and configured with an account/extension.Affected if SIP is enabled and the device has an active SIP account configured
-
Determine network accessibilityCheck the device's IP configuration. Use the device's web interface or network scan to confirm it has a valid IP address and is reachable on the network.Affected if The device has an IP address and is accessible on the network (even behind NAT)
-
Verify SIP NOTIFY handling is activeObserve SIP traffic using a packet capture tool (such as Wireshark) on the network segment where the device resides. Send a test SIP NOTIFY message to the device and observe if it processes it without validating Call-ID, branch, and tag parameters.Affected if The device accepts and processes incoming SIP NOTIFY messages without proper session validation
A user is affected if they have a Grandstream BudgeTone 100 device with SIP enabled and accessible on the network, as all firmware versions fail to validate SIP NOTIFY message parameters.
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 dataReplace affected Grandstream BudgeTone 100 phones with current VoIP devices from vendors providing regular security updates, as this hardware is end-of-life and no vendor patch exists.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-2182 — 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-2005-2182 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