Discover the impact of CVE-2017-18179 where Progress Sitefinity 9.1 uses a non-expiring authentication token, wrap_access_token, allowing unauthorized access even after password changes. Learn about the fix in version 10.1.
Progress Sitefinity 9.1 utilizes a non-expiring authentication token, wrap_access_token, which remains valid even after password changes or session terminations. This token is transmitted as a GET parameter. The vulnerability has been addressed in version 10.1.
Understanding CVE-2017-18179
In this section, we will delve into the details of the CVE-2017-18179 vulnerability.
What is CVE-2017-18179?
CVE-2017-18179 refers to the use of wrap_access_token in Progress Sitefinity 9.1 as an authentication token that does not expire, posing a security risk.
The Impact of CVE-2017-18179
The vulnerability allows the authentication token to remain valid even after critical security events like password changes or session terminations, potentially leading to unauthorized access.
Technical Details of CVE-2017-18179
Let's explore the technical aspects of CVE-2017-18179.
Vulnerability Description
Progress Sitefinity 9.1 uses wrap_access_token as an authentication token that does not expire, creating a security loophole.
Affected Systems and Versions
Exploitation Mechanism
The vulnerability arises from the non-expiring nature of the wrap_access_token and its transmission as a GET parameter, allowing for potential unauthorized access.
Mitigation and Prevention
Learn how to mitigate and prevent the CVE-2017-18179 vulnerability.
Immediate Steps to Take
Long-Term Security Practices
Patching and Updates