| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in Greasemonkey 0.3.3. Affected by this vulnerability is the function api. The manipulation results in information disclosure.
This vulnerability was named CVE-2005-2455. In addition, an exploit is available.
The affected component should be upgraded.
Details
A vulnerability classified as problematic has been found in Greasemonkey 0.3.3. Affected is the function api. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
Greasemonkey before 0.3.5 allows remote web servers to (1) read arbitrary files via a GET request to a file:// URL in the GM_xmlhttpRequest API function, (2) list installed scripts using GM_scripts, or obtain sensitive information via (3) GM_setValue and GM_getValue.
The weakness was presented 07/18/2005 (Website). The advisory is available at greaseblog.blogspot.com. This vulnerability is traded as CVE-2005-2455. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
The exploit is shared for download at frsirt.com. It is declared as proof-of-concept.
Upgrading to version 0.3.5 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (21453), Exploit-DB (26017), SecurityFocus (BID 14336†), OSVDB (18154†) and Secunia (SA16128†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Greasemonkey 0.3.5
Timeline
07/18/2005 🔍07/20/2005 🔍
07/20/2005 🔍
07/21/2005 🔍
08/04/2005 🔍
08/04/2005 🔍
01/18/2011 🔍
03/11/2015 🔍
11/22/2024 🔍
Sources
Advisory: greaseblog.blogspot.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2005-2455 (🔍)
GCVE (CVE): GCVE-0-2005-2455
GCVE (VulDB): GCVE-100-25938
X-Force: 21453
SecurityFocus: 14336 - Greasemonkey Multiple Remote Information Disclosure Vulnerabilities
Secunia: 16128
OSVDB: 18154 - Greasemonkey Extension for Mozilla Firefox Arbitrary File Access
SecurityTracker: 1014529
Vulnerability Center: 29213 - Greasemonkey Before 0.3.5 Remote Information Disclosure Vulnerability via a GET Request, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2015 23:39Updated: 11/22/2024 02:40
Changes: 03/11/2015 23:39 (50), 03/13/2017 10:05 (11), 07/05/2021 14:48 (4), 11/07/2024 09:30 (19), 11/22/2024 02:40 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.