What is the severity of CVE-2017-6683?

CVE-2017-6683 has been rated as a high severity vulnerability due to its potential for arbitrary command execution.

How do I fix CVE-2017-6683?

To fix CVE-2017-6683, it is recommended to upgrade Cisco Elastic Services Controller to a version that is not affected by this vulnerability.

What systems are affected by CVE-2017-6683?

CVE-2017-6683 specifically affects Cisco Elastic Services Controller version 2.2(9.76).

Is CVE-2017-6683 a remote vulnerability?

Yes, CVE-2017-6683 is a remote vulnerability that requires authentication to exploit.

Vulnerability/
CVE-2017-6683

critical

CWE

13/6/2017

23/6/2017

CVE-2017-6683: OS Command Injection

First published: Tue Jun 13 2017(Updated: )

A vulnerability in the esc_listener.py script of Cisco Elastic Services Controllers could allow an authenticated, remote attacker to execute arbitrary commands as the tomcat user on an affected system, aka an Authentication Request Processing Arbitrary Command Execution Vulnerability. More Information: CSCvc76642. Known Affected Releases: 2.2(9.76).

Credit: ykramarz@cisco.com

Affected Software	Affected Version	How to fix
Cisco Elastic Services Controller	=2.2\(9.76\)

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-6683?
CVE-2017-6683 has been rated as a high severity vulnerability due to its potential for arbitrary command execution.
How do I fix CVE-2017-6683?
To fix CVE-2017-6683, it is recommended to upgrade Cisco Elastic Services Controller to a version that is not affected by this vulnerability.
What systems are affected by CVE-2017-6683?
CVE-2017-6683 specifically affects Cisco Elastic Services Controller version 2.2(9.76).
What type of attack does CVE-2017-6683 allow?
CVE-2017-6683 allows an authenticated, remote attacker to execute arbitrary commands as the tomcat user on affected systems.
Is CVE-2017-6683 a remote vulnerability?
Yes, CVE-2017-6683 is a remote vulnerability that requires authentication to exploit.

collector/nvd-index
agent/severity
agent/weakness
agent/references
agent/author
agent/tags
agent/type
agent/description
agent/event
agent/softwarecombine
vendor/cisco
canonical/cisco elastic services controller
version/cisco elastic services controller/2.2\(9.76\)

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-6683?
CVE-2017-6683 has been rated as a high severity vulnerability due to its potential for arbitrary command execution.
How do I fix CVE-2017-6683?
To fix CVE-2017-6683, it is recommended to upgrade Cisco Elastic Services Controller to a version that is not affected by this vulnerability.
What systems are affected by CVE-2017-6683?
CVE-2017-6683 specifically affects Cisco Elastic Services Controller version 2.2(9.76).
What type of attack does CVE-2017-6683 allow?
CVE-2017-6683 allows an authenticated, remote attacker to execute arbitrary commands as the tomcat user on affected systems.
Is CVE-2017-6683 a remote vulnerability?
Yes, CVE-2017-6683 is a remote vulnerability that requires authentication to exploit.

CVE-2017-6683: OS Command Injection

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-6683?

How do I fix CVE-2017-6683?

What systems are affected by CVE-2017-6683?

What type of attack does CVE-2017-6683 allow?

Is CVE-2017-6683 a remote vulnerability?

Company

Resources

Contact

Frequently Asked Questions

What is the severity of CVE-2017-6683?

How do I fix CVE-2017-6683?

What systems are affected by CVE-2017-6683?

What type of attack does CVE-2017-6683 allow?

Is CVE-2017-6683 a remote vulnerability?