| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in SGI IRIX 6.3/6.5. The impacted element is an unknown function of the component crontab. Performing a manipulation results in privileges management. This vulnerability was named CVE-2000-0579. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability was found in SGI IRIX 6.3/6.5 (Operating System). It has been classified as problematic. This affects some unknown processing of the component crontab. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
IRIX crontab creates temporary files with predictable file names and with the umask of the user, which could allow local users to modify another user s crontab file as it is being edited.
The issue has been introduced in 09/01/1996. The weakness was presented 06/21/2000 by Jose Nazario (Website). The advisory is shared at archives.neohapsis.com. This vulnerability is uniquely identified as CVE-2000-0579. The exploitability is told to be difficult. 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 T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1389 days. During that time the estimated underground price was around $0-$5k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 1413†). See VDB-15692 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Support
- end of life (old version)
Website
- Vendor: http://www.sgi.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.7
VulDB Base Score: 4.9
VulDB Temp Score: 4.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: Privileges managementCWE: CWE-269 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
09/01/1996 🔍06/21/2000 🔍
06/21/2000 🔍
06/21/2000 🔍
06/25/2014 🔍
04/11/2019 🔍
Sources
Vendor: sgi.comAdvisory: archives.neohapsis.com
Researcher: Jose Nazario
Status: Not defined
CVE: CVE-2000-0579 (🔍)
GCVE (CVE): GCVE-0-2000-0579
GCVE (VulDB): GCVE-100-15693
SecurityFocus: 1413 - IRIX cron and crontab Predictable /tmp Filename Vulnerability
See also: 🔍
Entry
Created: 06/25/2014 12:53Updated: 04/11/2019 11:22
Changes: 06/25/2014 12:53 (55), 04/11/2019 11:22 (1)
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.