dbcve.org
Openstage SipApplication · Unify

CVE-2014-8421

HIGH · 7.5 CVSS v3.1 Published 2018-04-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 (former Siemens) OpenStage SIP and OpenScape Desk Phone IP V3 devices before R3.32.0 allow remote attackers to gain super-user privileges by leveraging SSH access and incorrect ownership of (1) ConfigureCoreFile.sh, (2) Traceroute.sh, (3) apps.sh, (4) conversion_java2native.sh, (5) coreCompression.sh, (6) deletePasswd.sh, (7) findHealthSvcFDs.sh, (8) fw_printenv.sh, (9) fw_setenv.sh, (10) hw_wd_kicker.sh, (11) new_rootfs.sh, (12) opera_killSnmpd.sh, (13) opera_startSnmpd.sh, (14) rebootOperaSoftware.sh, (15) removeLogFiles.sh, (16) runOperaServices.sh, (17) setPasswd.sh, (18) startAccTestSvcs.sh, (19) usbNotification.sh, or (20) appWeb in /Opera_Deploy.

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

This is a privilege escalation vulnerability in Unify OpenStage SIP and OpenScape Desk Phone IP V3 devices. Attackers with SSH access can gain super-user (root) privileges due to incorrect file ownership on 20 shell scripts in the /Opera_Deploy directory, including scripts like ConfigureCoreFile.sh, setPasswd.sh, and rebootOperaSoftware.sh.

MitigationUpgrade device firmware to version R3.32.0 or later which corrects the file ownership permissions. Until upgraded, restrict SSH access to trusted administrative personnel only.

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 SipApplication
Affected:< r3.32.0
Openscape Desk Phone Ip SipApplication
Affected:< r3.32.0

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

CVSS:3.1/AV:N/AC:H/PR:L/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 device model
    Access the device admin interface or check device labeling to confirm it is a Unify OpenStage SIP or OpenScape Desk Phone IP V3 model
    Affected if Device is not one of these two models
  2. Check firmware version
    Access the device admin interface (typically via web UI) or use the phone's built-in status menu to view the firmware version. Compare against r3.32.0
    Affected if Firmware version is r3.32.0 or later (not affected); version is below r3.32.0 (potentially affected)
  3. Verify SSH access is enabled
    Check the device configuration to see if SSH/telnet access is enabled. This is typically found in the device web interface under network settings or security settings
    Affected if SSH is disabled - attacker cannot exploit; SSH is enabled - vulnerability is accessible to attackers with SSH credentials
  4. Inspect /Opera_Deploy directory script ownership
    If SSH access is available, connect to the device and run: ls -la /Opera_Deploy/*.sh to check file ownership. Scripts should be owned by root but not writable by other users
    Affected if Scripts are owned by root but have world-writable permissions or are owned by a non-root user, indicating the vulnerability is present

Device is affected if it is an Unify OpenStage SIP or OpenScape Desk Phone IP V3 with firmware version below r3.32.0 and SSH access is enabled, allowing attackers to modify scripts in /Opera_Deploy for privilege escalation

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade device firmware to version R3.32.0 or later which corrects the file ownership permissions. Until upgraded, restrict SSH access to trusted administrative personnel only.

Fix this in Openstage Sip Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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