CVE-2006-0375
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 · uneditedAdvantage Century Telecommunication (ACT) P202S IP Phone 1.01.21 running firmware 1.1.21 on VxWorks uses a hardcoded Network Time Protocol (NTP) server in Taiwan, which could allow remote attackers to provide false time information, block access to time information, or conduct other attacks.
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 confidenceThe ACT P202S IP Phone firmware uses a hardcoded NTP server address pointing to a server in Taiwan. This hardcoded value cannot be changed by administrators, meaning the device relies on an external, untrusted time source that could be compromised or made unavailable, potentially affecting time-dependent operations and authentication.
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.01.21_firmware_1.1.21CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 modelLocate the IP phone device and confirm it is an ACT P202S or Advantage Century Telecommunication P202s model. Check the device label, web interface, or administrative console for the exact model designation.Affected if The device is an ACT P202S or Advantage Century Telecommunication P202s
-
Check the installed firmware versionAccess the device web interface or administrative console and navigate to the firmware or system information section. Record the exact firmware version number displayed.Affected if The firmware version matches 1.01.21 or firmware_1.1.21
-
Verify NTP server configuration accessibilityNavigate to the NTP or time settings section of the device administrative interface. Attempt to locate a field for configuring a custom NTP server address and determine whether the value can be modified or is read-only.Affected if The NTP server address field is absent, hidden, or read-only with no option to change the server
-
Inspect the configured NTP server addressIn the NTP settings section, record the currently configured NTP server hostname or IP address. Document any server address that appears preset or hardcoded.Affected if An NTP server address is hardcoded and points to an external untrusted source that cannot be altered
The device is affected if it is an ACT P202S or Advantage Century Telecommunication P202s running firmware 1.01.21 with a non-configurable NTP server address pointing to an untrusted external source.
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 dataConfigure the device to use a trusted internal NTP server, or if the firmware does not support NTP server configuration, update to firmware that provides this capability or implement network-level controls to intercept and redirect NTP traffic to a trusted time source.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-0375 — 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-2006-0375 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