dbcve.org
Snom 300 FirmwareOperating system · Snom

CVE-2009-1048

CRITICAL · 9.8 CVSS v3.1 Published 2009-08-14
Fix available
A fix is available. Upgrade to 6.5.20 / 7.1.39 or later.
See remediation →
100/100
Remediation priority · Urgent
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
The web interface on the snom VoIP phones snom 300, snom 320, snom 360, snom 370, and snom 820 with firmware 6.5 before 6.5.20, 7.1 before 7.1.39, and 7.3 before 7.3.14 allows remote attackers to bypass authentication, and reconfigure the phone or make arbitrary use of the phone, via a (1) http or (2) https request with 127.0.0.1 in the Host header.

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 confidence

The snom VoIP phone web interface contains an authentication bypass vulnerability where remote attackers can bypass authentication by sending HTTP/HTTPS requests with '127.0.0.1' in the Host header. This allows unauthenticated attackers to reconfigure the phone or make arbitrary use of the device.

MitigationUpgrade snom phone firmware to version 6.5.20, 7.1.39, or 7.3.14 or later to patch the authentication bypass vulnerability. Restrict network access to the web interface where possible.

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
Snom 300 FirmwareOperating system
Affected:>= 6.5, < 6.5.20>= 7.1, < 7.1.39>= 7.3, < 7.3.14
Snom 320 FirmwareOperating system
Affected:>= 6.5, < 6.5.20>= 7.1, < 7.1.39>= 7.3, < 7.3.14
Snom 360 FirmwareOperating system
Affected:>= 6.5, < 6.5.20>= 7.1, < 7.1.39>= 7.3, < 7.3.14
Snom 370 FirmwareOperating system
Affected:>= 6.5, < 6.5.20>= 7.1, < 7.1.39>= 7.3, < 7.3.14
Snom 820 FirmwareOperating system
Affected:>= 6.5, < 6.5.20>= 7.1, < 7.1.39>= 7.3, < 7.3.14

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 the snom phone model
    Access the phone's web interface and navigate to Status or Settings page, or send a SIP OPTIONS request to the device to read the User-Agent or Server header in the response
    Affected if The device is a Snom 300, 320, 360, 370, or 820 model
  2. Determine the installed firmware version
    In the web interface, go to Status > System Information or similar page to view the firmware version. Alternatively, check the SIP response headers for firmware information
    Affected if The firmware version falls within any of these ranges: >=6.5 and <6.5.20, OR >=7.1 and <7.1.39, OR >=7.3 and <7.3.14
  3. Verify the web interface is enabled
    Attempt to access the phone's HTTP/HTTPS web interface on the configured IP address. Check the phone's network settings to confirm the web server is enabled
    Affected if The web interface is accessible over HTTP or HTTPS on the network
  4. Confirm remote network access to the web interface
    Send an HTTP request to the phone from an external IP address (not from 127.0.0.1). Check whether the web interface is bound to all interfaces or only localhost in the phone's network configuration
    Affected if The web interface is reachable from remote network locations (not localhost-only)

You are affected if you have a Snom 300, 320, 360, 370, or 820 phone running firmware version 6.5.x before 6.5.20, 7.1.x before 7.1.39, or 7.3.x before 7.3.14, AND the web interface is accessible over the network.

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.

dbcve · scoped
Upgrade available Upgrade to 6.5.20 / 7.1.39 / 7.3.14 or later
Fixed in 6.5.207.1.397.3.14
Interim mitigation

Upgrade snom phone firmware to version 6.5.20, 7.1.39, or 7.3.14 or later to patch the authentication bypass vulnerability. Restrict network access to the web interface where possible.

Recommended fix High confidence

Firmware 6.5.20, 7.1.39, or 7.3.14 (or any later version within the same branch)

  1. 1. Identify the current firmware version of the Snom phone by accessing the web interface or checking the device settings
  2. 2. Determine which firmware branch your current version belongs to (6.5.x, 7.1.x, or 7.3.x)
  3. 3. Download the appropriate fixed firmware version from the official Snom support website: upgrade to 6.5.20 or later for 6.5.x branch, 7.1.39 or later for 7.1.x branch, or 7.3.14 or later for 7.3.x branch
  4. 4. Upload and install the new firmware through the phone's web interface under 'Maintenance' > 'Firmware' or via the provisioning server
  5. 5. After upgrade, verify the authentication bypass vulnerability is resolved by confirming the web interface requires valid credentials

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snom 300 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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