| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in OpenBSD up to 3.2. This issue affects some unknown processing of the file chpass of the component Temp File Handler. This manipulation causes information disclosure. The identification of this vulnerability is CVE-2003-1366. Furthermore, there is an exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability has been found in OpenBSD up to 3.2 (Operating System) and classified as problematic. Affected by this vulnerability is some unknown functionality of the file chpass of the component Temp File Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
chpass in OpenBSD 2.0 through 3.2 allows local users to read portions of arbitrary files via a hard link attack on a temporary file used to store user database information.
The weakness was shared 12/31/2003 by Marc Bevand (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2003-1366 since 10/16/2007. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1592 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at X-Force (11233), Exploit-DB (22210), SecurityFocus (BID 6748†) and SecurityTracker (ID 1006035†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.1VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.1
VulDB Temp Score: 4.6
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: 🔍
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
02/03/2003 🔍02/03/2003 🔍
12/31/2003 🔍
12/31/2003 🔍
10/16/2007 🔍
08/28/2014 🔍
12/23/2024 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Marc Bevand
Status: Confirmed
CVE: CVE-2003-1366 (🔍)
GCVE (CVE): GCVE-0-2003-1366
GCVE (VulDB): GCVE-100-21289
X-Force: 11233 - OpenBSD chpass user database information disclosure
SecurityFocus: 6748
SecurityTracker: 1006035
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/28/2014 18:01Updated: 12/23/2024 16:17
Changes: 08/28/2014 18:01 (49), 06/16/2018 10:14 (10), 12/23/2024 16:17 (25)
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.