dbcve.org
Openstage 80 FirmwareOperating system · Atos

CVE-2014-2651

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 SIP before V3 R3.11.0 has an authentication bypass in the default mode of the Workpoint 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

The Unify OpenStage and OpenScape Desk Phone IP SIP devices running firmware versions before V3 R3.11.0 contain an authentication bypass vulnerability in the default mode of the Workpoint Interface, allowing unauthenticated attackers to potentially gain unauthorized access to the phone system.

MitigationUpgrade the affected phone firmware to V3 R3.11.0 or later to remediate the authentication bypass. If immediate patching is not feasible, consider network segmentation and disabling the Workpoint Interface default mode if operationally acceptable.

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
    Check the physical device label, web interface, or admin menu to confirm the model is one of: OpenStage 20, OpenStage 20 E, OpenStage 40, OpenStage 40 G, OpenStage 60, OpenStage 60 G, OpenStage 80, or OpenStage 80 G
    Affected if The device model is any of the listed OpenStage models
  2. Check the firmware version
    Access the phone's web interface or admin menu and locate the firmware version information. Look for a version string indicating V3 and compare it to V3 R3.11.0
    Affected if The firmware version is V3 but earlier than V3 R3.11.0 (including any V2 or earlier versions)
  3. Verify Workpoint Interface configuration
    Access the phone's admin web interface or configuration menu and locate the Workpoint Interface settings. Check whether it is enabled and in default mode
    Affected if The Workpoint Interface is enabled and operating in default mode

A user is affected if they have any of the listed OpenStage phone models running firmware V3 versions earlier than V3 R3.11.0 with the Workpoint Interface enabled in its default configuration, allowing unauthenticated access.

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

Upgrade the affected phone firmware to V3 R3.11.0 or later to remediate the authentication bypass. If immediate patching is not feasible, consider network segmentation and disabling the Workpoint Interface default mode if operationally acceptable.

Recommended fix High confidence

V3 R3.11.0 or later

  1. Identify the exact current firmware version of the affected OpenStage phone by accessing the phone's web interface or admin menu
  2. Navigate to the official Unify support portal (networks.unify.com or assets.yourcircuit.com) and download the V3 R3.11.0 or later firmware for your specific OpenStage model
  3. Access the phone's administrative web interface and locate the firmware upgrade section
  4. Upload and apply the V3 R3.11.0 or later firmware file following the on-screen instructions
  5. Allow the phone to complete the firmware upgrade and reboot process
  6. Verify the new firmware version is V3 R3.11.0 or later in the phone's about/status section
  7. Confirm the Workpoint Interface authentication is now properly functioning
Caveat Firmware upgrades may reset some configurations; backup current settings before upgrading if possible

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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