What is the severity of CVE-2017-2683?

CVE-2017-2683 has been classified as a medium severity vulnerability due to the potential for a non-privileged user to execute a persistent XSS attack.

How do I fix CVE-2017-2683?

To fix CVE-2017-2683, upgrade the Siemens Ruggedcom NMS software to version 1.2 or later.

Who is affected by CVE-2017-2683?

Any non-privileged user of the Siemens Ruggedcom NMS versions prior to 1.2 is affected by CVE-2017-2683.

What can happen if CVE-2017-2683 is exploited?

Exploitation of CVE-2017-2683 could allow an attacker to perform Cross-Site Scripting attacks, potentially leading to the compromise of administrative permissions.

What are the vulnerable versions of Siemens Ruggedcom NMS for CVE-2017-2683?

The vulnerable versions of Siemens Ruggedcom NMS for CVE-2017-2683 are versions prior to 1.2, specifically up to 2.0.2.

Vulnerability/
CVE-2017-2683

high

8.2

CWE

27/2/2017

5/8/2024

CVE-2017-2683: XSS

First published: Mon Feb 27 2017(Updated: )

A non-privileged user of the Siemens web application RUGGEDCOM NMS < V1.2 on port 8080/TCP and 8081/TCP could perform a persistent Cross-Site Scripting (XSS) attack, potentially resulting in obtaining administrative permissions.

Credit: productcert@siemens.com

Affected Software	Affected Version	How to fix
Siemens Ruggedcom NMS	<=2.0.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-2683?
CVE-2017-2683 has been classified as a medium severity vulnerability due to the potential for a non-privileged user to execute a persistent XSS attack.
How do I fix CVE-2017-2683?
To fix CVE-2017-2683, upgrade the Siemens Ruggedcom NMS software to version 1.2 or later.
Who is affected by CVE-2017-2683?
Any non-privileged user of the Siemens Ruggedcom NMS versions prior to 1.2 is affected by CVE-2017-2683.
What can happen if CVE-2017-2683 is exploited?
Exploitation of CVE-2017-2683 could allow an attacker to perform Cross-Site Scripting attacks, potentially leading to the compromise of administrative permissions.
What are the vulnerable versions of Siemens Ruggedcom NMS for CVE-2017-2683?
The vulnerable versions of Siemens Ruggedcom NMS for CVE-2017-2683 are versions prior to 1.2, specifically up to 2.0.2.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/weakness
agent/severity
agent/last-modified-date
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/siemens
canonical/siemens ruggedcom nms
version/siemens ruggedcom nms/2.0.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-2683?
CVE-2017-2683 has been classified as a medium severity vulnerability due to the potential for a non-privileged user to execute a persistent XSS attack.
How do I fix CVE-2017-2683?
To fix CVE-2017-2683, upgrade the Siemens Ruggedcom NMS software to version 1.2 or later.
Who is affected by CVE-2017-2683?
Any non-privileged user of the Siemens Ruggedcom NMS versions prior to 1.2 is affected by CVE-2017-2683.
What can happen if CVE-2017-2683 is exploited?
Exploitation of CVE-2017-2683 could allow an attacker to perform Cross-Site Scripting attacks, potentially leading to the compromise of administrative permissions.
What are the vulnerable versions of Siemens Ruggedcom NMS for CVE-2017-2683?
The vulnerable versions of Siemens Ruggedcom NMS for CVE-2017-2683 are versions prior to 1.2, specifically up to 2.0.2.