CVE-2008-1249
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 · uneditedsnomControl.swf in the central phone server for the Snom 320 SIP Phone allows remote attackers to cause a denial of service (application crash and corruption of call logs) via a "'); (double quote, quote, close parenthesis, semicolon) sequence in the "Call a number" field.
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 snomControl.swf Flash component in Snom 320 SIP Phone central server fails to properly validate input in the 'Call a number' field. The injection sequence "'); allows an attacker to break out of context and cause application crash and corruption of call logs through the embedded Flash application's improper handling of user-supplied data.
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 dataall versionsCVSS 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
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/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.
-
Confirm device is a Snom 320 SIP PhoneAccess the device web interface or check device identification via SIP NOTIFY or HTTP request to the phone's IP address. Look for 'snom 320' or 'Snom 320' in the server header or web page content.Affected if The device identifies itself as a Snom 320 SIP Phone
-
Verify snomControl.swf is presentNavigate to the phone's web interface and look for the snomControl.swf file, typically found at paths like /snomControl.swf or within the /flash/ directory of the web server.Affected if The snomControl.swf Flash file is accessible on the device's web server
-
Confirm Flash-based control is enabledAccess the phone's web interface and locate the 'Call a number' field or dial pad functionality that uses the snomControl.swf component. Check if the Flash interface loads and accepts input.Affected if The Flash-based control interface with the 'Call a number' field is accessible and functional
-
Check web interface accessibilityAttempt HTTP/HTTPS access to the phone's management interface IP address. Verify the administrative or user-facing web pages are reachable.Affected if The web interface is accessible from the network (local or remote)
-
Identify if the vulnerable input field accepts special charactersIn the Flash component's 'Call a number' field, attempt to input the sequence "'); to observe if the application properly handles or rejects the injection.Affected if The application accepts the injection sequence without proper sanitization, potentially causing unexpected behavior
If the device is a Snom 320 with the snomControl.swf Flash component accessible and its 'Call a number' feature enabled, the environment is affected by this vulnerability.
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 dataApply vendor patch for snomControl.swf if available; otherwise, restrict network access to the phone management interface or disable the Flash-based control component as a compensating control.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1249 — 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-2008-1249 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