CVE-2007-4553
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 Thomson ST 2030 SIP phone with software 1.52.1 allows remote attackers to cause a denial of service (device hang) via an INVITE message with a Via header that contains a '/' (slash) instead of the required space following the SIP version number.
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 Thomson ST 2030 SIP phone software 1.52.1 contains a parsing vulnerability in its SIP protocol handler. The Via header parser fails to properly handle an INVITE message when a slash character ('/') appears instead of the required space after the SIP version number, causing the device to become unresponsive (hang).
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= 1CVSS 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
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 Thomson ST 2030 phones on the networkScan your network for SIP devices or check your VoIP inventory/phone book for Thomson ST 2030 handsets. Look for devices advertising 'Thomson' or 'ST 2030' in their SIP user-agent or DHCP fingerprint.Affected if Thomson ST 2030 SIP phones are present on the network
-
Verify the firmware versionAccess the phone's web interface or admin console and check the firmware/version information. The affected version is 1.52.1. Compare your installed version to this specific release.Affected if The device runs firmware version 1.52.1
-
Confirm SIP traffic is enabledCheck if the device has SIP signaling enabled and is registered to a SIP proxy/ registrar. The vulnerability triggers when the phone processes a malformed INVITE message, so SIP must be active.Affected if SIP protocol handling is enabled and the phone can receive INVITE requests
-
Monitor for malformed Via headersCapture SIP traffic heading to the phone and inspect INVITE messages. Look at the Via header format - it should contain 'SIP/2.0' with a space, not a slash. A malformed header would have 'SIP/2.0/' with a slash after the version before the space or transport type.Affected if The device receives SIP INVITE messages with a slash character '/' appearing after 'SIP/2.0' instead of the proper space separator in the Via header
You are affected if you have Thomson ST 2030 phones running firmware version 1.52.1 with SIP enabled, and they can receive SIP INVITE messages containing malformed Via headers (using '/' instead of space after the SIP version number).
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 dataIf vendor firmware update available, update all Thomson ST 2030 phones to patched version; otherwise implement SIP-aware firewall or session border controller to validate and reject malformed Via headers before reaching endpoint devices.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4553 — 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-4553 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