| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Paul Vixie Cron 3.0.1.56. This affects the function strcpy of the component Username Handler. The manipulation with the input aaaaaaaaaaaaaaaaaaaaa leads to memory corruption.
This vulnerability is documented as CVE-2001-0560. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Paul Vixie Cron 3.0.1.56. This issue affects the function strcpy of the component Username Handler. The manipulation with the input value aaaaaaaaaaaaaaaaaaaaa 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 Vixie cron 3.0.1-56 and earlier could allow a local attacker to gain additional privileges via a long username (> 20 characters).
The bug was discovered 02/10/2001. The weakness was released 02/10/2001 by flatline (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2001-0560. 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.
The vulnerability scanner Nessus provides a plugin with the ID 61896 (Mandrake Linux Security Advisory : vixie-cron (MDKSA-2001:022)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Mandriva Local Security Checks and running in the context l.
Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (6098), Tenable (61896) and OSVDB (5583†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.9
VulDB Temp Score: 5.7
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 |
Nessus ID: 61896
Nessus Name: Mandrake Linux Security Advisory : vixie-cron (MDKSA-2001:022)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
02/10/2001 🔍02/10/2001 🔍
02/20/2001 🔍
08/22/2001 🔍
04/09/2004 🔍
09/06/2012 🔍
07/08/2014 🔍
04/30/2019 🔍
Sources
Advisory: securityfocus.com⛔Researcher: flatline
Status: Not defined
CVE: CVE-2001-0560 (🔍)
GCVE (CVE): GCVE-0-2001-0560
GCVE (VulDB): GCVE-100-17201
X-Force: 6098
OSVDB: 5583 - Vixie Cron Long Username Overflow
Entry
Created: 07/08/2014 13:21Updated: 04/30/2019 10:46
Changes: 07/08/2014 13:21 (63), 04/30/2019 10:46 (2)
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.