| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Piwik up to 0.2.6. The affected element is an unknown function of the file Cookie.php. Executing a manipulation can lead to config. This vulnerability is handled as CVE-2011-0400. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability was found in Piwik up to 0.2.6. It has been declared as problematic. This vulnerability affects an unknown part of the file Cookie.php. The manipulation with an unknown input leads to a config vulnerability. The CWE definition for the vulnerability is CWE-16. As an impact it is known to affect confidentiality. CVE summarizes:
Cookie.php in Piwik before 1.1 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http session.
The bug was discovered 11/02/2010. The weakness was released 01/04/2011 (Website). The advisory is shared for download at piwik.org. This vulnerability was named CVE-2011-0400 since 01/10/2011. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.004.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:Cookie.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 0.2.7 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (64639), SecurityFocus (BID 45787†) and OSVDB (70382†). Entries connected to this vulnerability are available at VDB-55997, VDB-55995 and VDB-55994. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: ConfigCWE: CWE-16
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Piwik 0.2.7
Timeline
11/02/2010 🔍11/03/2010 🔍
01/04/2011 🔍
01/10/2011 🔍
01/10/2011 🔍
01/12/2011 🔍
01/12/2011 🔍
03/19/2015 🔍
10/11/2021 🔍
Sources
Advisory: 1795Status: Not defined
Confirmation: 🔍
CVE: CVE-2011-0400 (🔍)
GCVE (CVE): GCVE-0-2011-0400
GCVE (VulDB): GCVE-100-55996
X-Force: 64639
SecurityFocus: 45787 - Piwik Prior to 1.1 Multiple Security Vulnerabilities
OSVDB: 70382 - Piwik Cookie.php HTTPS Session Cookie Secure Flag Weakness
See also: 🔍
Entry
Created: 03/19/2015 23:27Updated: 10/11/2021 10:55
Changes: 03/19/2015 23:27 (55), 02/08/2019 15:05 (5), 10/11/2021 10:55 (3)
Complete: 🔍
Cache ID: 216:1B4:103
No comments yet. Languages: en.
Please log in to comment.