CVE-2007-1590
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 · uneditedThe Grandstream BudgeTone 200 IP phone, with program 1.1.1.14 and bootloader 1.1.1.5, allows remote attackers to cause a denial of service (device crash) via SIP (1) INVITE, (2) CANCEL, or unspecified other messages with a WWW-Authenticate header containing a crafted Digest domain.
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 200 IP phone (firmware 1.1.1.14, bootloader 1.1.1.5) suffers from a denial-of-service vulnerability where remote attackers can crash the device by sending SIP messages (INVITE, CANCEL, or other) containing a malformed WWW-Authenticate header with a crafted Digest domain.
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= 1.1.1.5= 1.1.1.14CVSS 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
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify the device modelAccess the device's web interface or check the device label to confirm it is a Grandstream BudgeTone 200 IP phone.Affected if The device is a Grandstream BudgeTone 200 model.
-
Check the firmware versionLog into the device web interface and navigate to the status or system information page to view the firmware version. Alternatively, check the boot loader version during device startup or via the admin interface.Affected if The firmware version is 1.1.1.14 or the bootloader version is 1.1.1.5.
-
Confirm SIP service is enabledVerify that SIP (Session Initiation Protocol) is enabled on the device. Check the device configuration under VoIP settings or SIP settings in the web administration panel.Affected if SIP service is enabled and the device is configured to process SIP requests.
-
Determine network accessibility of SIP portCheck if the device SIP port (typically UDP/TCP port 5060) is exposed to untrusted networks. Scan the network to see if port 5060 is listening on interfaces accessible from outside the trusted network segment.Affected if The SIP port is reachable from an untrusted or external network.
A user is affected if they operate a Grandstream BudgeTone 200 with firmware 1.1.1.14 or bootloader 1.1.1.5, have SIP enabled, and the SIP service is network-accessible to remote attackers.
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 dataGiven the age of this vulnerability (2007) and likely end-of-life status of the device, the primary remediation is device replacement with a supported model. If the device must remain in service, implement network segmentation to isolate VoIP devices and apply SIP traffic filtering at the network edge to block malicious requests.
- 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-2007-1590 — 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-2007-1590 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