| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Mercurial 1.0.1 and classified as critical. This impacts an unknown function. Performing a manipulation results in access control. This vulnerability is cataloged as CVE-2008-4297. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, was found in Mercurial 1.0.1. This affects an unknown part. 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:
Mercurial before 1.0.2 does not enforce the allowpull permission setting for a pull operation from hgweb, which allows remote attackers to read arbitrary files from a repository via an "hg pull" request.
The weakness was shared 09/27/2008 (Website). The advisory is shared at issues.rpath.com. This vulnerability is uniquely identified as CVE-2008-4297 since 09/26/2008. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 40066 (openSUSE Security Update : mercurial (mercurial-230)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks.
Upgrading to version 1.0.1 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (45229), Tenable (40066), SecurityFocus (BID 31223†), Secunia (SA32182†) and Vulnerability Center (SBV-22963†). If you want to get the best quality for vulnerability data then you always have to consider 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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 40066
Nessus Name: openSUSE Security Update : mercurial (mercurial-230)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Mercurial 1.0.1
Timeline
08/13/2008 🔍09/26/2008 🔍
09/27/2008 🔍
09/27/2008 🔍
09/27/2008 🔍
10/07/2008 🔍
07/21/2009 🔍
07/28/2009 🔍
03/17/2015 🔍
08/02/2021 🔍
Sources
Advisory: issues.rpath.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2008-4297 (🔍)
GCVE (CVE): GCVE-0-2008-4297
GCVE (VulDB): GCVE-100-44229
X-Force: 45229
SecurityFocus: 31223 - Mercurial hgweb 'allowpull' Information Disclosure Vulnerability
Secunia: 32182 - SUSE update for mercurial, Less Critical
Vulnerability Center: 22963 - Mercurial \x3C 1.0.2 Allows Remote Attackers to Read Files from a Repository via \, Medium
Vupen: ADV-2008-2604
Entry
Created: 03/17/2015 16:11Updated: 08/02/2021 09:59
Changes: 03/17/2015 16:11 (56), 02/12/2017 12:52 (13), 08/02/2021 09:59 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.