CVE-2017-2207
First published: Fri Jun 09 2017(Updated: )
Untrusted search path vulnerability in the installer of SaAT Personal ver.1.0.10.272 and earlier allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.
Credit: vultures@jpcert.or.jp
| Affected Software | Affected Version | How to fix |
|---|---|---|
| SaAT Personal | <=1.0.10.272 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-2207?
CVE-2017-2207 has a medium severity level due to its untrusted search path vulnerability that can lead to privilege escalation.
How do I fix CVE-2017-2207?
To fix CVE-2017-2207, update SaAT Personal to version 1.0.10.273 or later to ensure that the untrusted search path vulnerability is mitigated.
What versions of SaAT Personal are affected by CVE-2017-2207?
SaAT Personal versions 1.0.10.272 and earlier are affected by CVE-2017-2207.
What type of attack does CVE-2017-2207 enable?
CVE-2017-2207 enables privilege escalation attacks by allowing the execution of a Trojan horse DLL.
Is there a workaround for CVE-2017-2207 if I can't apply the update immediately?
A potential workaround for CVE-2017-2207 is to prevent unauthorized access to directories that may be used for DLL placement.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/severity
- agent/references
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/saat
- canonical/saat personal
- version/saat personal/1.0.10.272