CVE-2000-0964
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 · uneditedBuffer overflow in the web administration service for the HiNet LP5100 IP-phone allows remote attackers to cause a denial of service and possibly execute arbitrary commands via a long GET request.
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 confidenceBuffer overflow vulnerability in the web administration interface of the HiNet LP5100 IP-phone device. Exploitable remotely via specially crafted long HTTP GET requests, allowing attackers to crash the service (DoS) or potentially execute arbitrary commands.
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= 5100.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Identify the device modelCheck the physical device label or access the device's web interface to confirm the model is HiNet LP5100. The device is an IP-phone with embedded web administration capabilities.Affected if The device is not a HiNet LP5100 model, then this CVE does not apply.
-
Determine the firmware versionAccess the device's web administration interface and navigate to the status or system information page to retrieve the firmware/software version number.Affected if The installed version is exactly 5100.0, indicating the specific affected release.
-
Verify web admin interface is enabledAttempt to access the device's web administration port (typically HTTP on port 80 or 8080) to confirm the interface is running and responding to requests.Affected if The web administration interface is accessible and responding, making the buffer overflow exploitable.
-
Check network exposure of web admin portPerform a port scan or review firewall rules to determine if the web administration port is exposed to untrusted networks or the internet.Affected if The web admin port is externally accessible from untrusted networks, increasing the likelihood of remote exploitation.
You are affected if you have a HiNet LP5100 device running firmware version 5100.0 with the web administration interface enabled and exposed to network paths where attackers could send malicious HTTP GET requests.
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 dataSince this is a legacy hardware device (circa 2000) likely beyond vendor support, recommended actions include: disabling or blocking access to the web administration port externally, network isolating affected devices, or replacing end-of-life devices with current hardware.
- Consultation4.0 h
- Implementation8.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 $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0964 — 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-2000-0964 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