Sun Solaris 2.5.1/2.6/7.0 Terminal /usr/bin/write Long Argument memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Sun Solaris 2.5.1/2.6/7.0. This affects an unknown function of the file /usr/bin/write of the component Terminal. The manipulation as part of Long Argument leads to memory corruption. This vulnerability is documented as CVE-1999-1371. Additionally, an exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Sun Solaris 2.5.1/2.6/7.0 (Operating System). It has been rated as critical. This issue affects an unknown functionality of the file /usr/bin/write of the component Terminal. The manipulation as part of a Long Argument 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 /usr/bin/write in Solaris 2.6 and 7 allows local users to gain privileges via a long string in the terminal name argument.
The weakness was released 03/08/1999 as not defined posting (Bugtraq). The advisory is shared at marc.theaimsgroup.com. The identification of this vulnerability is CVE-1999-1371. 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 as well as a public exploit are known.
The exploit is available at securiteam.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (7546), Exploit-DB (256) and OSVDB (8660†). Entries connected to this vulnerability are available at VDB-14563 and VDB-14557. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Support
- end of life (old version)
Website
- Vendor: https://www.oracle.com/sun/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.3VulDB Meta Temp Score: 8.4
VulDB Base Score: 9.3
VulDB Temp Score: 8.4
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: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
03/08/1999 🔍03/08/1999 🔍
04/09/2004 🔍
06/20/2014 🔍
12/29/2024 🔍
Sources
Vendor: oracle.comAdvisory: marc.theaimsgroup.com
Status: Confirmed
CVE: CVE-1999-1371 (🔍)
GCVE (CVE): GCVE-0-1999-1371
GCVE (VulDB): GCVE-100-14561
X-Force: 7546 - Sun Solaris /usr/bin/write buffer overflow
OSVDB: 8660 - Solaris /usr/bin/write Second Argument Local Overflow
SecuriTeam: securiteam.com
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 06/20/2014 22:53Updated: 12/29/2024 10:59
Changes: 06/20/2014 22:53 (56), 05/20/2018 11:17 (8), 12/29/2024 10:59 (18)
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.