| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in reportbug 2.60/2.61/3.2. The affected element is an unknown function. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2005-0625. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in reportbug 2.60/2.61/3.2 (Reporting Software). This affects an unknown functionality. 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. The summary by CVE is:
reportbug 3.2 includes settings from .reportbugrc in bug reports which exposes sensitive information such as smtpuser and smtppasswd.
The weakness was disclosed 02/28/2005 (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is uniquely identified as CVE-2005-0625 since 03/02/2005. The exploitability is told to be easy. An attack has to be approached locally. 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 T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (19520), SecurityFocus (BID 12674†) and Secunia (SA14422†). The entry VDB-23996 is pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.0VulDB Meta Temp Score: 4.0
VulDB Base Score: 4.0
VulDB Temp Score: 4.0
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: Partially
Local: Yes
Remote: No
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/28/2005 🔍02/28/2005 🔍
02/28/2005 🔍
02/28/2005 🔍
03/02/2005 🔍
03/10/2015 🔍
07/01/2021 🔍
Sources
Advisory: marc.theaimsgroup.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2005-0625 (🔍)
GCVE (CVE): GCVE-0-2005-0625
GCVE (VulDB): GCVE-100-23997
X-Force: 19520 - reportbug \
SecurityFocus: 12674
Secunia: 14422 - Debian reportbug Exposure of Sensitive Information, Less Critical
See also: 🔍
Entry
Created: 03/10/2015 15:27Updated: 07/01/2021 13:12
Changes: 03/10/2015 15:27 (48), 07/06/2018 08:25 (7), 07/01/2021 13:12 (4)
Complete: 🔍
Cache ID: 216:7A4: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.