| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in GNU Bash 1.4.17/2.0.0. This impacts an unknown function of the component Directory Name Handler. This manipulation causes memory corruption. This vulnerability is handled as CVE-1999-1048. Additionally, an exploit exists. It is advised to implement further authentication.
Details
A vulnerability classified as critical was found in GNU Bash 1.4.17/2.0.0. Affected by this vulnerability is an unknown code of the component Directory Name Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Buffer overflow in bash 2.0.0, 1.4.17, and other versions allows local attackers to gain privileges by creating an extremely large directory name, which is inserted into the password prompt via the \w option in the PS1 environmental variable when another user changes into that directory.
The weakness was released 09/05/1998 by Joao Manuel Carolino as not defined posting (Bugtraq). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-1999-1048. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are unknown but an exploit is available.
After 22 hours, there has been an exploit disclosed. It is possible to download the exploit at archives.neohapsis.com. It is declared as proof-of-concept.
It is possible to mitigate the problem by adding an authentication mechanism.
The vulnerability is also documented in the databases at X-Force (3414) and OSVDB (8345†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian GNU Linux
- Red Hat Linux
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.gnu.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.9
VulDB Temp Score: 5.2
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: AuthenticationStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
09/05/1998 🔍09/05/1998 🔍
09/05/1998 🔍
04/09/2004 🔍
06/19/2014 🔍
04/17/2026 🔍
Sources
Vendor: gnu.orgAdvisory: marc.theaimsgroup.com
Researcher: Joao Manuel Carolino
Status: Not defined
CVE: CVE-1999-1048 (🔍)
GCVE (CVE): GCVE-0-1999-1048
GCVE (VulDB): GCVE-100-14221
X-Force: 3414 - Linux bash buffer overflow
OSVDB: 8345 - bash \w option PS1 Environment Variable Overflow
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/19/2014 17:31Updated: 04/17/2026 16:04
Changes: 06/19/2014 17:31 (54), 04/03/2019 21:27 (5), 04/17/2026 16:04 (22)
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.