First published: Wed Jan 29 2014(Updated: )
CiviCRM 2.0.0 through 4.2.9 and 4.3.0 through 4.3.3 does not properly enforce role-based access control (RBAC) restrictions for default custom searches, which allows remote authenticated users with the "access CiviCRM" permission to bypass intended access restrictions, as demonstrated by accessing custom contribution data without having the "access CiviContribute" permission.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
CiviCRM | =2.0.0 | |
CiviCRM | =2.0.1 | |
CiviCRM | =2.0.2 | |
CiviCRM | =2.0.3 | |
CiviCRM | =2.0.4 | |
CiviCRM | =2.0.5 | |
CiviCRM | =2.0.6 | |
CiviCRM | =2.0.7 | |
CiviCRM | =2.1.0 | |
CiviCRM | =2.1.1 | |
CiviCRM | =2.1.2 | |
CiviCRM | =2.1.4 | |
CiviCRM | =2.1.6 | |
CiviCRM | =2.2.0 | |
CiviCRM | =2.2.1 | |
CiviCRM | =2.2.2 | |
CiviCRM | =2.2.3 | |
CiviCRM | =2.2.5 | |
CiviCRM | =2.2.6 | |
CiviCRM | =2.2.7 | |
CiviCRM | =2.2.8 | |
CiviCRM | =2.2.9 | |
CiviCRM | =3.0.0 | |
CiviCRM | =3.0.1 | |
CiviCRM | =3.0.2 | |
CiviCRM | =3.0.3 | |
CiviCRM | =3.0.4 | |
CiviCRM | =3.1.1 | |
CiviCRM | =3.1.2 | |
CiviCRM | =3.1.3 | |
CiviCRM | =3.1.4 | |
CiviCRM | =3.1.5 | |
CiviCRM | =3.1.6 | |
CiviCRM | =3.2.0 | |
CiviCRM | =3.2.1 | |
CiviCRM | =3.2.2 | |
CiviCRM | =3.2.3 | |
CiviCRM | =3.2.4 | |
CiviCRM | =3.2.5 | |
CiviCRM | =3.3.0 | |
CiviCRM | =3.3.1 | |
CiviCRM | =3.3.2 | |
CiviCRM | =3.3.3 | |
CiviCRM | =3.3.5 | |
CiviCRM | =3.3.6 | |
CiviCRM | =3.4.0 | |
CiviCRM | =4.0.5 | |
CiviCRM | =4.1.0 | |
CiviCRM | =4.1.1 | |
CiviCRM | =4.1.2 | |
CiviCRM | =4.1.3 | |
CiviCRM | =4.1.4 | |
CiviCRM | =4.1.5 | |
CiviCRM | =4.1.6 | |
CiviCRM | =4.2.0 | |
CiviCRM | =4.2.1 | |
CiviCRM | =4.2.2 | |
CiviCRM | =4.2.4 | |
CiviCRM | =4.2.5 | |
CiviCRM | =4.2.6 | |
CiviCRM | =4.2.7 | |
CiviCRM | =4.2.8 | |
CiviCRM | =4.2.9 | |
CiviCRM | =4.3.0 | |
CiviCRM | =4.3.1 | |
CiviCRM | =4.3.2 | |
CiviCRM | =4.3.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-4661 has a medium severity level due to improper role-based access control allowing authenticated users to bypass access restrictions.
To fix CVE-2013-4661, you should upgrade to CiviCRM version 4.3.4 or later, which addresses the access control issue.
CVE-2013-4661 affects CiviCRM versions 2.0.0 through 4.2.9 and 4.3.0 through 4.3.3.
While you can take precautions, it is highly recommended to upgrade to a secure version to fully mitigate the risk from CVE-2013-4661.
The primary attack vector for CVE-2013-4661 is remote authenticated users exploiting the lack of role-based access restrictions on custom searches.