dbcve.org
Openstage 80 FirmwareOperating system · Atos

CVE-2014-2650

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unify OpenStage / OpenScape Desk Phone IP before V3 R3.11.0 SIP has an OS command injection vulnerability in the web based management interface

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 confidence

Unify OpenStage and OpenScape Desk Phone IP devices running firmware versions before V3 R3.11.0 contain an OS command injection vulnerability in the web-based management interface. An unauthenticated remote attacker could inject and execute arbitrary operating system commands by sending specially crafted requests to the web management interface, potentially gaining full control over the affected device.

MitigationUpdate affected phone firmware to version V3 R3.11.0 or later. If immediate patching is not possible, restrict network access to the web management interface by placing phones in a separate VLAN or behind a firewall to limit exposure.

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
Openstage 80 FirmwareOperating system
Affected:= v3
Openstage 80 G FirmwareOperating system
Affected:= v3
Openstage 60 G FirmwareOperating system
Affected:= v3
Openstage 60 FirmwareOperating system
Affected:= v3
Openstage 40 FirmwareOperating system
Affected:= v3
Openstage 40 G FirmwareOperating system
Affected:= v3
Openstage 20 E FirmwareOperating system
Affected:= v3
Openstage 20 FirmwareOperating system
Affected:= v3

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 phone model
    Locate the device label or check the web management interface login page for the model name (OpenStage 20, 20E, 40, 40G, 60, 60G, 80, or 80G)
    Affected if The device is any of these OpenStage models from the V3 firmware line
  2. Check the installed firmware version
    Access the phone web interface or check the device administration menu for the firmware version information; compare it against the affected range (V3 R3.11.0 and later are fixed, earlier versions are vulnerable)
    Affected if The firmware version is V3 with a release prior to R3.11.0 (for example, V3 R2.x or earlier)
  3. Confirm the web management interface is enabled
    Attempt to access the device web interface by entering the phone IP address in a browser; if a login or management page loads, the interface is active
    Affected if The web-based management interface is accessible on the network (the vulnerability is exploitable only when this interface is enabled)

You are affected if you have an OpenStage phone running firmware V3 R3.10.x or earlier AND the web management interface is enabled and reachable on your 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected phone firmware to version V3 R3.11.0 or later. If immediate patching is not possible, restrict network access to the web management interface by placing phones in a separate VLAN or behind a firewall to limit exposure.

Recommended fix Moderate confidence

V3 R3.11.0 SIP

  1. Access the phone's web-based management interface by entering the device's IP address in a web browser
  2. Navigate to the Administration or Settings section of the web interface
  3. Locate the Firmware or Software Update option
  4. Check current firmware version to confirm it is below V3 R3.11.0
  5. Download the V3 R3.11.0 SIP firmware update from the official Unify/Siemens support portal (assets.yourcircuit.com or networks.unify.com)
  6. In the web interface, use the firmware upload/update function to apply the V3 R3.11.0 SIP firmware file
  7. Wait for the firmware upload to complete and for the device to reboot
  8. After reboot, verify the new firmware version is V3 R3.11.0 or later in the web interface
Caveat Standard firmware upgrade - ensure backup of configuration if available; phone may briefly reboot during update

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

Fix this in Openstage 80 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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