Skip to content

Mautic Sessions could be hijacked due to tracking contacts by an auto-incremented ID

High severity GitHub Reviewed Published Jan 19, 2021 in mautic/mautic • Updated Sep 11, 2023

Package

composer mautic/core (Composer)

Affected versions

< 2.13.0

Patched versions

2.13.0

Description

Impact

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.

Patches

Update to 2.13.0 or later

Workarounds

None

For more information

If you have any questions or comments about this advisory:

References

@RCheesley RCheesley published to mautic/mautic Jan 19, 2021
Reviewed Jan 19, 2021
Published to the GitHub Advisory Database Jan 19, 2021
Last updated Sep 11, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2018-10189

GHSA ID

GHSA-vfxj-qg93-7wwc

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.