Description
An issue was discovered in Mautic 1.x and 2.x before 2.13.0. It is possible to systematically emulate tracking cookies per contact due to tracking the contact by their auto-incremented ID. Thus, a third party can manipulate the cookie value with +1 to systematically assume being tracked as each contact in Mautic. It is then possible to retrieve information about the contact through forms that have progressive profiling enabled.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-0517 | An issue was discovered in Mautic 1.x and 2.x before 2.13.0. It is possible to systematically emulate tracking cookies per contact due to tracking the contact by their auto-incremented ID. Thus, a third party can manipulate the cookie value with +1 to systematically assume being tracked as each contact in Mautic. It is then possible to retrieve information about the contact through forms that have progressive profiling enabled. |
Github GHSA |
GHSA-vfxj-qg93-7wwc | Mautic Sessions could be hijacked due to tracking contacts by an auto-incremented ID |
References
| Link | Providers |
|---|---|
| https://github.com/mautic/mautic/releases/tag/2.13.0 |
|
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-09-17T00:31:14.792Z
Reserved: 2018-04-17T00:00:00.000Z
Link: CVE-2018-10189
No data.
Status : Modified
Published: 2018-04-17T20:29:00.410
Modified: 2024-11-21T03:40:58.783
Link: CVE-2018-10189
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA