| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in man 1.5 on Red Hat. Affected is the function ultimate_source. The manipulation leads to memory corruption.
This vulnerability is uniquely identified as CVE-2001-1028. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in man 1.5 on Red Hat. This issue affects the function ultimate_source. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in ultimate_source function of man 1.5 and earlier allows local users to gain privileges.
The weakness was disclosed 05/28/2001 (Website). The advisory is shared at redhat.com. The identification of this vulnerability is CVE-2001-1028. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at X-Force (8622). The entry VDB-16759 is pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.9
VulDB Base Score: 9.3
VulDB Temp Score: 8.9
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: Memory corruptionCWE: CWE-119
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
05/28/2001 🔍05/28/2001 🔍
07/04/2014 🔍
06/10/2024 🔍
Sources
Advisory: redhat.comStatus: Not defined
CVE: CVE-2001-1028 (🔍)
GCVE (CVE): GCVE-0-2001-1028
GCVE (VulDB): GCVE-100-16697
X-Force: 8622
See also: 🔍
Entry
Created: 07/04/2014 11:18Updated: 06/10/2024 04:32
Changes: 07/04/2014 11:18 (39), 04/08/2019 09:15 (9), 06/10/2024 04:32 (17)
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.