Piwigo up to 2.9.1 Session ws_session_logout Cookie session expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in Piwigo up to 2.9.1. This issue affects the function ws_session_logout of the component Session Handler. Such manipulation as part of Cookie leads to session expiration.
This vulnerability is listed as CVE-2017-9837. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in Piwigo up to 2.9.1 (Photo Gallery Software). It has been rated as problematic. Affected by this issue is the function ws_session_logout of the component Session Handler. The manipulation as part of a Cookie leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality, integrity, and availability. CVE summarizes:
The ws_session_logout function in Piwigo 2.9.1 and earlier does not properly delete user login cookies, which allows remote attackers to gain access via cookie reuse.
The bug was discovered 06/24/2017. The weakness was presented 06/24/2017 (Website). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2017-9837 since 06/24/2017. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-102787 for similar entry. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://github.com/Piwigo/Piwigo/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/24/2017 🔍06/24/2017 🔍
06/24/2017 🔍
06/24/2017 🔍
06/24/2017 🔍
12/09/2022 🔍
Sources
Product: github.comAdvisory: 717
Status: Not defined
CVE: CVE-2017-9837 (🔍)
GCVE (CVE): GCVE-0-2017-9837
GCVE (VulDB): GCVE-100-102788
See also: 🔍
Entry
Created: 06/25/2017 00:12Updated: 12/09/2022 07:16
Changes: 06/25/2017 00:12 (44), 10/20/2019 10:59 (1), 12/29/2020 16:34 (7), 12/09/2022 07:16 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.