What is the severity of CVE-2013-6773?

CVE-2013-6773 is classified as a medium severity vulnerability due to its ability to allow privilege escalation.

How do I fix CVE-2013-6773?

To mitigate CVE-2013-6773, ensure that the Splunk Universal Forwarder service path is correctly quoted to avoid unquoted service path vulnerabilities.

Which versions of Splunk are affected by CVE-2013-6773?

CVE-2013-6773 affects Splunk versions from 5.0 to 5.0.3.

Can CVE-2013-6773 affect my Windows system?

Yes, CVE-2013-6773 can affect Windows systems where Splunk 5.0.3 is installed and configured with an unquoted service path.

What should I do if I am using an affected version of Splunk with CVE-2013-6773?

If you are using an affected version of Splunk, it is recommended to upgrade to a later version or apply necessary patches that address this vulnerability.

Vulnerability/
CVE-2013-6773

high

7.8

CWE

269

23/1/2020

6/8/2024

CVE-2013-6773

First published: Thu Jan 23 2020(Updated: )

Splunk 5.0.3 has an Unquoted Service Path in Windows for Universal Forwarder which can allow an attacker to escalate privileges

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Splunk Splunk	>=5.0<5.0.3
Microsoft Windows

Never miss a vulnerability like this again

Reference Links

http://www.splunk.com/view/SP-CAAAHXG

Frequently Asked Questions

What is the severity of CVE-2013-6773?
CVE-2013-6773 is classified as a medium severity vulnerability due to its ability to allow privilege escalation.
How do I fix CVE-2013-6773?
To mitigate CVE-2013-6773, ensure that the Splunk Universal Forwarder service path is correctly quoted to avoid unquoted service path vulnerabilities.
Which versions of Splunk are affected by CVE-2013-6773?
CVE-2013-6773 affects Splunk versions from 5.0 to 5.0.3.
Can CVE-2013-6773 affect my Windows system?
Yes, CVE-2013-6773 can affect Windows systems where Splunk 5.0.3 is installed and configured with an unquoted service path.
What should I do if I am using an affected version of Splunk with CVE-2013-6773?
If you are using an affected version of Splunk, it is recommended to upgrade to a later version or apply necessary patches that address this vulnerability.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/last-modified-date
agent/weakness
agent/author
agent/severity
agent/event
agent/description
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/splunk
canonical/splunk splunk
version/splunk splunk/5.0
vendor/microsoft
canonical/microsoft windows

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-2013-6773?
CVE-2013-6773 is classified as a medium severity vulnerability due to its ability to allow privilege escalation.
How do I fix CVE-2013-6773?
To mitigate CVE-2013-6773, ensure that the Splunk Universal Forwarder service path is correctly quoted to avoid unquoted service path vulnerabilities.
Which versions of Splunk are affected by CVE-2013-6773?
CVE-2013-6773 affects Splunk versions from 5.0 to 5.0.3.
Can CVE-2013-6773 affect my Windows system?
Yes, CVE-2013-6773 can affect Windows systems where Splunk 5.0.3 is installed and configured with an unquoted service path.
What should I do if I am using an affected version of Splunk with CVE-2013-6773?
If you are using an affected version of Splunk, it is recommended to upgrade to a later version or apply necessary patches that address this vulnerability.