Acquia commons 6.x-2.4/6.x-2.5/6.x-2.6/6.x-2.7/6.x-2.x Access Restriction commons_discussion_views_default_views access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Acquia commons 6.x-2.4/6.x-2.5/6.x-2.6/6.x-2.7/6.x-2.x and classified as problematic. Impacted is the function commons_discussion_views_default_views of the component Access Restriction. Performing a manipulation results in access control.
This vulnerability was named CVE-2012-4483. There is no available exploit.
The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in Acquia commons 6.x-2.4/6.x-2.5/6.x-2.6/6.x-2.7/6.x-2.x. This affects the function commons_discussion_views_default_views of the component Access Restriction. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality. The summary by CVE is:
The commons_discussion_views_default_views function in modules/features/commons_discussion/commons_discussion.views_default.inc in the Drupal Commons module 6.x-2.x before 6.x-2.8 for Drupal does not properly enforce intended node access restrictions, which might allow remote attackers to obtain sensitive information via the recent comments listing.
The weakness was presented 10/31/2012 (Website). The advisory is shared at drupalcode.org. This vulnerability is uniquely identified as CVE-2012-4483 since 08/21/2012. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 6.x-2.x eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: commons 6.x-2.x
Timeline
08/21/2012 🔍10/31/2012 🔍
10/31/2012 🔍
03/24/2015 🔍
02/23/2019 🔍
Sources
Advisory: drupalcode.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2012-4483 (🔍)
GCVE (CVE): GCVE-0-2012-4483
GCVE (VulDB): GCVE-100-62793
Entry
Created: 03/24/2015 12:22Updated: 02/23/2019 08:47
Changes: 03/24/2015 12:22 (48), 02/23/2019 08:47 (2)
Complete: 🔍
Cache ID: 216:CC2:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.