dbcve.org
Ht488Hardware / appliance · Grandstream

CVE-2007-5788

HIGH · 7.1 CVSS v2.0 Published 2007-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Buffer overflow in the SIP parser on the Grandstream HT-488 0.1 allows remote attackers to cause a denial of service (device crash) via a crafted SIP INVITE 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 · moderate confidence

A buffer overflow vulnerability exists in the SIP parser of Grandstream HT-488 version 0.1. The vulnerability is triggered by sending a specially crafted SIP INVITE message containing oversized data that overflows a fixed-size buffer, causing the device to crash.

MitigationSince this is a legacy device from 2007 likely reaching end-of-life, primary mitigation involves network-based controls (restrict SIP traffic to trusted sources, implement firewall rules) and device replacement if no firmware update is available.

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
Ht488Hardware / appliance
Affected:= 0.1

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
M
Authentication
None
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/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 checks

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

  1. Identify Grandstream HT-488 device on network
    Scan network for devices with Grandstream HT-488 MAC OUI (00:0B:82) or check device inventory for this specific model
    Affected if Device model is Grandstream HT-488 and is present on the network
  2. Check device firmware version
    Access device web interface or check via SNMP/sysinfo to verify firmware version is 0.1
    Affected if Firmware version equals 0.1 exactly
  3. Verify SIP service is enabled
    Check device configuration via web UI or config file for SIP proxy settings and registration status
    Affected if SIP functionality is enabled and configured with a SIP proxy/server
  4. Check network exposure of SIP port
    Scan for open UDP/TCP port 5060 (SIP) on the device and verify if accessible from untrusted networks
    Affected if SIP port 5060 is exposed to untrusted network segments or the internet

Environment is affected if a Grandstream HT-488 running firmware version 0.1 has SIP enabled and the SIP port is accessible from untrusted network sources.

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

Since this is a legacy device from 2007 likely reaching end-of-life, primary mitigation involves network-based controls (restrict SIP traffic to trusted sources, implement firewall rules) and device replacement if no firmware update is available.

Fix this in Ht488 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-5788 — 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-2007-5788 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