What is the severity of CVE-2015-8251?

The severity of CVE-2015-8251 is considered high due to potential remote code execution risks.

How do I fix CVE-2015-8251?

To fix CVE-2015-8251, update the firmware of affected OpenStage and OpenScape Desk Phone models to the latest version.

Which devices are affected by CVE-2015-8251?

CVE-2015-8251 affects various models including OpenStage 60, OpenScape Desk Phone IP 55G, and others running firmware version 3.0.

Is CVE-2015-8251 being actively exploited?

As of the latest updates, there are no confirmed active exploits for CVE-2015-8251 in the wild.

What are the potential consequences of CVE-2015-8251?

The potential consequences of CVE-2015-8251 include unauthorized access, interception of communications, and execution of arbitrary code.

Vulnerability/
CVE-2015-8251

medium

5.9

CWE

200

25/9/2017

6/8/2024

CVE-2015-8251: Infoleak

First published: Mon Sep 25 2017(Updated: )

OpenStage 60 and OpenScape Desk Phone IP 55G SIP V3, OpenStage 15, 20E, 20 and 40 and OpenScape Desk Phone IP 35G SIP V3, OpenScape Desk Phone IP 35G Eco SIP V3, OpenStage 60 and OpenScape Desk Phone IP 55G HFA V3, OpenStage 15, 20E, 20, and 40 and OpenScape Desk Phone IP 35G HFA V3, and OpenScape Desk Phone IP 35G Eco HFA V3 use non-unique X.509 certificates and SSH host keys.

Credit: cret@cert.org

Affected Software	Affected Version	How to fix
Atos Openstage 60 Firmware	=3.0
Unify Openstage 60
Unify Openscape Desk Phone Ip 55g Sip Firmware	=3.0
Unify Openscape Desk Phone Ip 55g Sip
Unify Openstage 15 Firmware	=3.0
Unify Openstage 15
Unify Openstage 20e Firmware	=3.0
Unify Openstage 20e
Unify Openstage 20 Firmware	=3.0
Unify Openstage 20
Unify Openstage 40 Firmware	=3.0
Atos Openstage 40
Unify Openscape Desk Phone Ip 35g Sip Firmware	=3.0
Unify Openscape Desk Phone Ip 35g Sip
Unify Openscape Desk Phone Ip 35g Eco Sip Firmware	=3.0
Unify Openscape Desk Phone Ip 35g Eco Sip
Unify Openscape Desk Phone Ip 55g Hfa Firmware	=3.0
Atos Openscape Desk Phone IP 55G
Unify Openscape Desk Phone Ip 35g Hfa Firmware	=3.0
Unify Openscape Desk Phone Ip 35g Hfa
Unify Openscape Desk Phone Ip 35g Eco Hfa

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-8251?
The severity of CVE-2015-8251 is considered high due to potential remote code execution risks.
How do I fix CVE-2015-8251?
To fix CVE-2015-8251, update the firmware of affected OpenStage and OpenScape Desk Phone models to the latest version.
Which devices are affected by CVE-2015-8251?
CVE-2015-8251 affects various models including OpenStage 60, OpenScape Desk Phone IP 55G, and others running firmware version 3.0.
Is CVE-2015-8251 being actively exploited?
As of the latest updates, there are no confirmed active exploits for CVE-2015-8251 in the wild.
What are the potential consequences of CVE-2015-8251?
The potential consequences of CVE-2015-8251 include unauthorized access, interception of communications, and execution of arbitrary code.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/last-modified-date
agent/weakness
agent/description
agent/event
agent/first-publish-date
agent/source
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/unify
canonical/atos openstage 60 firmware
version/atos openstage 60 firmware/3.0
canonical/unify openstage 60
canonical/unify openscape desk phone ip 55g sip firmware
version/unify openscape desk phone ip 55g sip firmware/3.0
canonical/unify openscape desk phone ip 55g sip
canonical/unify openstage 15 firmware
version/unify openstage 15 firmware/3.0
canonical/unify openstage 15
canonical/unify openstage 20e firmware
version/unify openstage 20e firmware/3.0
canonical/unify openstage 20e
canonical/unify openstage 20 firmware
version/unify openstage 20 firmware/3.0
canonical/unify openstage 20
canonical/unify openstage 40 firmware
version/unify openstage 40 firmware/3.0
canonical/atos openstage 40
canonical/unify openscape desk phone ip 35g sip firmware
version/unify openscape desk phone ip 35g sip firmware/3.0
canonical/unify openscape desk phone ip 35g sip
canonical/unify openscape desk phone ip 35g eco sip firmware
version/unify openscape desk phone ip 35g eco sip firmware/3.0
canonical/unify openscape desk phone ip 35g eco sip
canonical/unify openscape desk phone ip 55g hfa firmware
version/unify openscape desk phone ip 55g hfa firmware/3.0
canonical/atos openscape desk phone ip 55g
canonical/unify openscape desk phone ip 35g hfa firmware
version/unify openscape desk phone ip 35g hfa firmware/3.0
canonical/unify openscape desk phone ip 35g hfa
canonical/unify openscape desk phone ip 35g eco hfa

Frequently Asked Questions

What is the severity of CVE-2015-8251?
The severity of CVE-2015-8251 is considered high due to potential remote code execution risks.
How do I fix CVE-2015-8251?
To fix CVE-2015-8251, update the firmware of affected OpenStage and OpenScape Desk Phone models to the latest version.
Which devices are affected by CVE-2015-8251?
CVE-2015-8251 affects various models including OpenStage 60, OpenScape Desk Phone IP 55G, and others running firmware version 3.0.
Is CVE-2015-8251 being actively exploited?
As of the latest updates, there are no confirmed active exploits for CVE-2015-8251 in the wild.
What are the potential consequences of CVE-2015-8251?
The potential consequences of CVE-2015-8251 include unauthorized access, interception of communications, and execution of arbitrary code.

CVE-2015-8251: Infoleak

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-8251?

How do I fix CVE-2015-8251?

Which devices are affected by CVE-2015-8251?

Is CVE-2015-8251 being actively exploited?

What are the potential consequences of CVE-2015-8251?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2015-8251?

How do I fix CVE-2015-8251?

Which devices are affected by CVE-2015-8251?

Is CVE-2015-8251 being actively exploited?

What are the potential consequences of CVE-2015-8251?