Piwik up to 0.2.32 access control

Summaryinfo

A vulnerability classified as problematic has been found in Piwik up to 0.2.32. Impacted is an unknown function. This manipulation causes access control. This vulnerability is registered as CVE-2009-1085. No exploit is available.

Detailsinfo

A vulnerability classified as problematic was found in Piwik up to 0.2.32. Affected by this vulnerability is some unknown processing. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality. The summary by CVE is:

Piwik 0.2.32 and earlier stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain the API key and other sensitive information via a direct request for misc/cron/archive.sh.

The weakness was published 03/25/2009 (oss-sec). The advisory is shared at openwall.com. This vulnerability is known as CVE-2009-1085 since 03/25/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Piwik

Version

• 0.2.25
• 0.2.26
• 0.2.27
• 0.2.28
• 0.2.29
• 0.2.30
• 0.2.31
• 0.2.32

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion