What is the severity of CVE-2017-11747?

CVE-2017-11747 is classified as a medium severity vulnerability due to its potential impact on local user permissions.

How do I fix CVE-2017-11747?

To mitigate CVE-2017-11747, update Tinyproxy to version 1.8.5 or later, which addresses this issue.

What type of vulnerability is CVE-2017-11747?

CVE-2017-11747 is a privilege escalation vulnerability.

Who is affected by CVE-2017-11747?

CVE-2017-11747 affects all versions of Tinyproxy up to and including 1.8.4.

What can an attacker do with CVE-2017-11747?

An attacker can exploit CVE-2017-11747 to modify the tinyproxy.pid file and potentially kill arbitrary processes.

Vulnerability/
CVE-2017-11747

medium

5.5

CWE

269

30/7/2017

31/3/2020

CVE-2017-11747

First published: Sun Jul 30 2017(Updated: )

main.c in Tinyproxy 1.8.4 and earlier creates a /run/tinyproxy/tinyproxy.pid file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for tinyproxy.pid modification before a root script executes a "kill `cat /run/tinyproxy/tinyproxy.pid`" command.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Tinyproxy	<=1.8.4

Remedy

https://github.com/tinyproxy/tinyproxy/issues/106

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-11747?
CVE-2017-11747 is classified as a medium severity vulnerability due to its potential impact on local user permissions.
How do I fix CVE-2017-11747?
To mitigate CVE-2017-11747, update Tinyproxy to version 1.8.5 or later, which addresses this issue.
What type of vulnerability is CVE-2017-11747?
CVE-2017-11747 is a privilege escalation vulnerability.
Who is affected by CVE-2017-11747?
CVE-2017-11747 affects all versions of Tinyproxy up to and including 1.8.4.
What can an attacker do with CVE-2017-11747?
An attacker can exploit CVE-2017-11747 to modify the tinyproxy.pid file and potentially kill arbitrary processes.

agent/severity
agent/references
agent/weakness
agent/author
agent/type
agent/tags
agent/event
agent/description
agent/remedy
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
vendor/tinyproxy project
canonical/tinyproxy
version/tinyproxy/1.8.4

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-11747?
CVE-2017-11747 is classified as a medium severity vulnerability due to its potential impact on local user permissions.
How do I fix CVE-2017-11747?
To mitigate CVE-2017-11747, update Tinyproxy to version 1.8.5 or later, which addresses this issue.
What type of vulnerability is CVE-2017-11747?
CVE-2017-11747 is a privilege escalation vulnerability.
Who is affected by CVE-2017-11747?
CVE-2017-11747 affects all versions of Tinyproxy up to and including 1.8.4.
What can an attacker do with CVE-2017-11747?
An attacker can exploit CVE-2017-11747 to modify the tinyproxy.pid file and potentially kill arbitrary processes.