What is the severity of CVE-2017-11162?

CVE-2017-11162 is classified as a high-severity vulnerability due to its potential for unauthorized access to sensitive files.

How do I fix CVE-2017-11162?

To fix CVE-2017-11162, you should upgrade Synology Photo Station to version 6.7.4-3433 or later for full protection.

What type of attack does CVE-2017-11162 protect against?

CVE-2017-11162 protects against directory traversal attacks that allow remote authenticated users to read arbitrary files.

Which versions of Synology Photo Station are affected by CVE-2017-11162?

CVE-2017-11162 affects Synology Photo Station versions prior to 6.7.4-3433 and 6.3-2968.

Who is at risk due to CVE-2017-11162?

Remote authenticated users who have access to vulnerable versions of Synology Photo Station are at risk due to CVE-2017-11162.

Vulnerability/
CVE-2017-11162

medium

6.5

CWE

8/9/2017

5/8/2024

CVE-2017-11162: Path Traversal

First published: Fri Sep 08 2017(Updated: )

Directory traversal vulnerability in synphotoio in Synology Photo Station before 6.7.4-3433 and 6.3-2968 allows remote authenticated users to read arbitrary files via unspecified vectors.

Credit: security@synology.com

Affected Software	Affected Version	How to fix
Synology Photo Station	<=6.3-2967
Synology Photo Station	<=6.7.3-3432

Never miss a vulnerability like this again

Reference Links

https://www.synology.com/en-global/support/security/Synology_SA_17_35_PhotoStation

Frequently Asked Questions

What is the severity of CVE-2017-11162?
CVE-2017-11162 is classified as a high-severity vulnerability due to its potential for unauthorized access to sensitive files.
How do I fix CVE-2017-11162?
To fix CVE-2017-11162, you should upgrade Synology Photo Station to version 6.7.4-3433 or later for full protection.
What type of attack does CVE-2017-11162 protect against?
CVE-2017-11162 protects against directory traversal attacks that allow remote authenticated users to read arbitrary files.
Which versions of Synology Photo Station are affected by CVE-2017-11162?
CVE-2017-11162 affects Synology Photo Station versions prior to 6.7.4-3433 and 6.3-2968.
Who is at risk due to CVE-2017-11162?
Remote authenticated users who have access to vulnerable versions of Synology Photo Station are at risk due to CVE-2017-11162.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/last-modified-date
agent/references
agent/tags
agent/severity
agent/weakness
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/synology
canonical/synology photo station
version/synology photo station/6.3-2967
version/synology photo station/6.7.3-3432

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-11162?
CVE-2017-11162 is classified as a high-severity vulnerability due to its potential for unauthorized access to sensitive files.
How do I fix CVE-2017-11162?
To fix CVE-2017-11162, you should upgrade Synology Photo Station to version 6.7.4-3433 or later for full protection.
What type of attack does CVE-2017-11162 protect against?
CVE-2017-11162 protects against directory traversal attacks that allow remote authenticated users to read arbitrary files.
Which versions of Synology Photo Station are affected by CVE-2017-11162?
CVE-2017-11162 affects Synology Photo Station versions prior to 6.7.4-3433 and 6.3-2968.
Who is at risk due to CVE-2017-11162?
Remote authenticated users who have access to vulnerable versions of Synology Photo Station are at risk due to CVE-2017-11162.