SourceForge Creammonkey 0.9/1.0/1.1 gm_xmlhttprequest access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in SourceForge Creammonkey 0.9/1.0/1.1. This affects the function gm_xmlhttprequest. This manipulation causes access control.
This vulnerability is registered as CVE-2007-6640. No exploit is available.
Details
A vulnerability was found in SourceForge Creammonkey 0.9/1.0/1.1. It has been declared as critical. Affected by this vulnerability is the function gm_xmlhttprequest. 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, and integrity. The summary by CVE is:
Creammonkey 0.9 through 1.1 and GreaseKit 1.2 through 1.3 does not properly prevent access to dangerous functions, which allows remote attackers to read the configuration, modify the configuration, or send an HTTP request via the (1) GM_addStyle, (2) GM_log, (3) GM_openInTab, (4) GM_setValue, (5) GM_getValue, or (6) GM_xmlhttpRequest function within a web page on which a userscript is configured.
The weakness was published 12/26/2007 (Website). The advisory is shared at osvdb.org. This vulnerability is known as CVE-2007-6640 since 01/03/2008. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability is also documented in the databases at X-Force (39272), OSVDB (42819†) and Secunia (SA28241†). 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: 6.5VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.5
VulDB Temp Score: 5.7
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: Unproven
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/26/2007 🔍12/26/2007 🔍
12/26/2007 🔍
01/03/2008 🔍
01/03/2008 🔍
03/16/2015 🔍
09/14/2018 🔍
Sources
Advisory: osvdb.org⛔Status: Confirmed
Confirmation: 🔍
CVE: CVE-2007-6640 (🔍)
GCVE (CVE): GCVE-0-2007-6640
GCVE (VulDB): GCVE-100-40345
X-Force: 39272 - GreaseKit and Creammonkey GM security bypass
Secunia: 28241 - GreaseKit / Creammonkey GM API Vulnerability, Less Critical
OSVDB: 42819 - GreaseKit / Creammonkey API Multiple GM Function Cross-site Request
Entry
Created: 03/16/2015 13:43Updated: 09/14/2018 08:08
Changes: 03/16/2015 13:43 (52), 09/14/2018 08:08 (5)
Complete: 🔍
Cache ID: 216::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.